E4S-Project / E4S-Project/testsuite
Git cloning in cinema test fails on internet-disabled compute nodes
Nobody has claimed this yet.
- Dominant language
- Fortran
- Stars
- 21
- Forks
- 33
- Avg merge
- 3m
- Merged PRs (30d)
- 1
Description
@EthanS94 @dhrogers
The cinema test as currently implemented can't run on systems that disable internet access from their compute nodes. Is there a reasonable subset of test code that can be permanently committed to the test suite or another way to execute a standalone test without cloning the whole repository?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the cinema test and the code path that clones the repository. Check how the test behaves on internet-disabled compute nodes, then determine whether a permanently committed subset or a standalone execution path can cover the same validation without cloning the whole repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100