Fix test_suite not being able to retrieve memory on systems that use cgroups v2#670
Fix test_suite not being able to retrieve memory on systems that use cgroups v2#670boegel merged 18 commits intoEESSI:2023.06-software.eessi.iofrom casparvl:fix_testsuite_azure
Conversation
|
Instance
|
|
Instance
|
|
Instance
|
|
bot: build repo:eessi.io-2023.06-software arch:zen4 |
Updates by the bot instance
|
Updates by the bot instance
|
|
New job on instance
|
Updates by the bot instance
|
|
bot: build repo:eessi.io-2023.06-software arch:zen4 |
Updates by the bot instance
|
Updates by the bot instance
|
|
New job on instance
|
Updates by the bot instance
|
|
Ok, need to debug further, it seems to get a memory limit of |
|
bot: build repo:eessi.io-2023.06-software arch:zen4 |
Updates by the bot instance
|
Updates by the bot instance
|
Updates by the bot instance
|
|
New job on instance
|
|
bot: build repo:eessi.io-2023.06-software arch:zen4 |
Updates by the bot instance
|
Updates by the bot instance
|
|
New job on instance
|
Updates by the bot instance
|
Updates by the bot instance
|
|
New job on instance
|
|
I'm confused. In the test step of the bot: How can that not exist, I just installed it didn't I? And the test step resumes from the correct tempdir: What's going on here? |
|
Tried manually, got: |
|
bot: build repo:eessi.io-2023.06-software arch:zen4 |
Updates by the bot instance
|
Updates by the bot instance
|
|
New job on instance
|
|
bot: build repo:eessi.io-2023.06-software arch:zen4 |
Updates by the bot instance
|
Updates by the bot instance
|
|
New job on instance
|
|
This looks the way it should be: |
…statements that were inserted just to debug this particular issue
|
Try once more, after some more changes for easier debugging in the future... |
|
bot: build repo:eessi.io-2023.06-software arch:zen4 |
Updates by the bot instance
|
Updates by the bot instance
|
|
New job on instance
|
|
Ok, this is better, we now also print the detected parameters and final config file. That makes for much easier debugging: |
|
And the actual test step for this one looks perfect: |
Fixes https://gitlab.com/eessi/support/-/issues/86