-
Notifications
You must be signed in to change notification settings - Fork 139
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
ntest_simulation_module failing without MPI #3120
Comments
Nexus assumes you are going to run MPI applications with it. MPI availability is basically a requirement then for a correct Nexus install, which this failing test exposes. For the purpose of running tests with QMCPACK "no MPI", perhaps a flag should be passed to |
I just tracked this down again, forgetting the answer was already here (rainy Friday).
A couple of questions around lightweight ways to improve the situation: Q. How should one use Nexus with no MPI library installed? If it is in practice today a requirement then we need to plan appropriately for installations and builds for workshops. Q. Why not check for mpirun on the path and skip this test if not found? Or ignore this error if mpirun is mentioned in the error? |
Nexus can be used w/o MPI, but that is not the typical use case. I think "tests pass" should imply "examples will work" and al the examples use MPI. I'm happy to supply e.g. a I likely also can improve the test failure message (exposed with |
We also use "tests pass" for installations though, so I think an update is needed to handle these cases. Suggestion to keep this super simple:
|
Describe the bug
https://cdash.qmcpack.org/CDash/testSummary.php?project=1&name=ntest_nexus_simulation_module&date=2021-04-20
The most recent updates #3108 fixed the mpi situation but not the no mpi situation.
Edit: Interestingly the Intel2019.1 build passed while gcc, llvm, and pgi builds did not. But perhaps enough of Intel MPI was picked up even though not enabled(???)
To Reproduce
Latest develop, software versions as nitrogen/sulfur. (ornl_versions.sh)
Expected behavior
Test passes
System:
module list
]Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: