-
Notifications
You must be signed in to change notification settings - Fork 48
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
{2023.06}[foss/2022a] ESPResSo v4.2.1 #331
Conversation
Instance
|
|
@maxim-masterov #310 should get done first? |
bot: build repo:eessi-2023.06-software arch:x86_64/generic |
Updates by the bot instance
|
New job on instance
|
New job on instance
|
For both jobs: bot: build repo:eessi-2023.06-software arch:x86_64/generic |
Updates by the bot instance
|
New job on instance
|
New job on instance
|
Wrong Python is being used:
May need to add additional CMake options like we did for VTK in easybuilders/easybuild-easyconfigs#16741 ? |
Incorporated changes in PR 18963 |
Let's take this for a spin, to verify whether the changes in easybuilders/easybuild-easyconfigs#18963 are sufficient to fix the problem with picking up the Python dependency... bot: build repo:eessi-2023.06-software arch:x86_64/generic |
Updates by the bot instance
|
New job on instance
|
New job on instance
|
New job on instance
|
Build still fails, same problem, so the |
New job on instance
|
New job on instance
|
New job on instance
|
New job on instance
|
New job on instance
|
Here are all statistical tests: They are known to take a large amount of time on our CI pipelines, because we run them concurrently and max out the host machine CPU resource usage via MPI oversubscription, so that hyperthreaded cores are fully used. This makes their runtime fluctuate wildly, with a negative feedback loop since they compete against one another for the same resources (e.g. if one test times out, there is a very good chance another unrelated test will time out too). More details can be found in espressomd/espresso#3883. Having said that, you don't seem to run these tests concurrently, so your CI pipelines should not be experiencing the issue I just described. Maybe there is a deeper issue in ESPResSo's MPI code, unfortunately timeout information alone is not sufficient for me to investigate an MPI issue. |
Updates by the bot instance
|
Updates by the bot instance
|
|
@boegel Do we have a false negative here? The only errors are related to finding
and I suspect this is related to the tests that we ignore. |
The
I'll see why that happens, and how to fix it... |
… missing installations
Problem caused by the "known issues" YAML file is fixed in 8779e8b. I'll re-trigger the builds (will take 1-1.5h again, but fine, I don't want to cut corners here). 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
|
New job on instance
|
New job on instance
|
New job on instance
|
New job on instance
|
New job on instance
|
New job on instance
|
all staging PRs merged, deployment under way... |
{2023.06}[foss/2023a] OpenFOAM v10
Add ESPResSo
Depends on:
edit (by @boegel, 2023-10-10):