-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run test suite #466
Run test suite #466
Conversation
Instance
|
…e easystack files to be able to trigger the bot building pipeline and see if the testing works
bot: build repo:eessi.io-2023.06-software arch:x86_64/amd/zen2 |
Updates by the bot instance
|
New job on instance
|
Well, it did run. But clearly I have to change things :D
That's clearly my Friday afternoon brain. Of course, if I want to use the EESSI environment, I should execute this stuff in the EESSI container. Point of attention here: I'll need to start the container in such a way that it picks up the installations it just created in the build step. I.e. with the correct workdir and everything. In the meantime: it should have reported failure for the test step, but I was grepping for too strict a pattern |
bot: build repo:eessi.io-2023.06-software arch:x86_64/amd/zen2 |
Updates by the bot instance
|
New job on instance
|
bot: build repo:eessi.io-2023.06-software arch:x86_64/amd/zen2 |
Updates by the bot instance
|
New job on instance
|
bot: build repo:eessi.io-2023.06-software arch:x86_64/amd/zen2 |
Updates by the bot instance
|
New job on instance
|
Closing in favour of #467 |
First attempt at actually trying to run the test suite in the
test.sh
step from the bot and having the result checked in thecheck-test.sh
step.My understanding of how the bot executes these steps is a bit limited though, so this will probably take a bit of trial and error before it does what it should do :)