{2023.06}[foss/2021a] ESPResSo v4.2.1#332
{2023.06}[foss/2021a] ESPResSo v4.2.1#332maxim-masterov wants to merge 8 commits intoEESSI:2023.06-pilot.eessi-hpc.orgfrom
Conversation
|
Instance
|
Where did the |
|
@maxim-masterov That comes from For now, ignore the CI failures (they'll fail anyway until this module is installed), and let's trigger a test build? It would be helpful if you first sync your PR branch here with current |
…o espresso_2021a
…ayer into espresso_2021a
|
bot: build repo:eessi-2023.06-software arch:x86_64/generic |
Updates by the bot instance
|
|
New job on instance
|
|
New job on instance
|
|
Incorporated changes in PR 18963 |
|
bot: build repo:eessi-2023.06-software arch:x86_64/generic |
Updates by the bot instance
|
Updates by the bot instance
|
|
New job on instance
|
|
New job on instance
|
|
bot: build repo:eessi-2023.06-software arch:aarch64/neoverse_v1 |
Updates by the bot instance
|
|
bot: show_config |
Updates by the bot instance
|
|
Instance
|
|
bot: build repo:eessi-hpc.org-2023.06-software arch:aarch64/neoverse_v1 |
Updates by the bot instance
|
|
New job on instance
|
|
The build that is failing is So, it's actually I've tried the build interactively on the |
|
Interactively, I do error out on the ESPResSo build btw... But we can worry about that later (if it occurs also when the bot does it). |
|
So, I've done a bit of reading. It fails in the Autocompleter for modules. That autocompleter has to create a cache first. It seems there is a timeout on that, controlled by this line. It might be that creation of this cache is indeed slow. Could be that it simply needs to crawl through a lot of CVMFS paths, which could be slow. Could be that going through the build dir is slow - I think the bot is building in a writeable overlay, which I believe may be a bit slow (also to read?). We could try to increase that TIMEOUT. Or skip the test. Or ignore the test failures... The only thing I can't really explain is why we haven't seen it with other |
|
@casparvl This sounded somewhat familiar, and it seems I have run into this as well a few years ago: |
|
I reproduced this issue now also interactively, by running the container with: and using the default I'll adapt my docs in this pr so that building in the writeable overlay is explained (instead of in |
|
I'm going to close this. We have ESPResSo now in the |
{2023.06}[foss/2023b] Qt5 v5.15.13
Add ESPResSo for 2021a without CUDA support