Run test suite#466
Run test suite#466casparvl wants to merge 6 commits intoEESSI:2023.06-software.eessi.iofrom casparvl:run_test_suite
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.shstep from the bot and having the result checked in thecheck-test.shstep.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 :)