generate test easyconfig without checksums to check whether checksums.json is picked up in test_checksum_step #26
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@mboisson Some cleanup for the tests in easybuilders#3749.
In general, it's better to avoid adding additional test easyconfigs if it can be avoided, since it complicates maintenance of the test suite, and may slow down the tests that iterate over all available test easyconfigs...
Also, I don't see the need to use
checksums-test.json
and copying that tochecksums.json
in the test, so I renamedtest_ecs/t/toy/checksums-test.json
totest_ecs/t/toy/checksums.json
.To avoid breaking the
test_enforce_checksums
, wherechecksums.json
is not supposed to be found, I've wiped$EASYBUILD_ROBOT_PATHS
in that test (since thentest_ecs/t/toy
is no longer consider byobtain_file
while it tries to findchecksums.json
.