Add docs on how to debug the test step that is run on the build node #158
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
trz42
requested changes
Jun 4, 2024
trz42
approved these changes
Jun 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Depends on: EESSI/software-layer#467
EESSI/software-layer#467 implements a test step as part of the build procedure, on the build node. Like the build, these tests can fail, and it is good to have some way to reproduce this locally.
This documentation provides instructions on how to run the test step locally. It is hard to guarantee an exact match with what happens in the CI, due to the environment being a factor (e.g. number of slots that mpirun sees depends on your environment). Nevertheless, with these instructions, one should be pretty close... close enough to (probably) reproduce most test failures.