add scripts to run test suite after build job has finished #366
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.
First outline of how testing could be added to build-and-deploy procedure. See also accompanying PR for the bot (EESSI/eessi-bot-software-layer#222).
This PR adds three scripts:
bot/test.sh
prepares the environment for running the tests inside the build containerbot/build.sh
andbot/inspect.sh
(for the latter see script to more easily inspect a build job #317)run_tests.sh
is just a small script that runstest_suite.sh
in a compat layer environment (very similar toinstall_software_layer.sh
)test_suite.sh
runs some testseb --sanity-check-only
for all easyconfigs that were "added" to an easystack file (by design, it will also process easyconfigs whose line has changed)EESSI-pilot-install-software.sh
TODO:
bot/check-test.sh
that processes the result of the test(s) and produces and update to be added to the PR comment (job status table); this is likely somewhat similar tobot/check-build.sh