-
Notifications
You must be signed in to change notification settings - Fork 706
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
make sure Python dependency included for ESPResSo is actually used by specifying -DPYTHON_EXECUTABLE
#18963
Conversation
-DPython3_EXECUTABLE
Worth clarifying: this is required in EESSI because there we have a very recent "system" Python (3.11) in the compat layer, which CMake happily prefers over the specific Python dependency we're providing. We saw the same problem with VTK (cfr. #16741), which suggests we should be automatically setting |
@boegelbot please test @ generoso |
@boegel: Request for testing this PR well received on login1 PR test command '
Test results coming soon (I hope)... - notification for comment with ID 1754879789 processed Message to humans: this is just bookkeeping information for me, |
Test report by @boegelbot |
@boegelbot please test @ jsc-zen2 |
@smoors: Request for testing this PR well received on jsczen2l1.int.jsc-zen2.easybuild-test.cluster PR test command '
Test results coming soon (I hope)... - notification for comment with ID 1755429652 processed Message to humans: this is just bookkeeping information for me, |
The latest build failure in EESSI/software-layer#331 (comment) shows that only adding So we need extra CMake options to make it behave. |
From CMake output, which shows that Python 3.11 from compat layer is picked up, instead of the provided dependency...
Looks like we also need to use It probably doesn't hurt to also specify See also https://cmake.org/cmake/help/latest/module/FindPython3.html |
Since ESPResSo 4.2.1 uses Yaay CMake! |
Wait, What... |
…thon version used by CMake when building ESPResSo
Switched to |
CMake ESPResSo 4.2 uses The latest ESPResSO code uses |
@branfosj Very little room for confusion there... Thanks for clearing that up! puts 🥃 away |
-DPython3_EXECUTABLE
-DPYTHON_EXECUTABLE
@boegelbot please test @ generoso |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tests in EESSI/software-layer#331 show that fix is working as intended (failure for aarch64/neoverse_v1
is due to known flaky tests in ESPResSo test suite)
@boegel: Request for testing this PR well received on login1 PR test command '
Test results coming soon (I hope)... - notification for comment with ID 1756944034 processed Message to humans: this is just bookkeeping information for me, |
Test report by @boegelbot |
Test report by @boegel |
The last build failed due to existing lock:
|
Test report by @boegel |
Going in, thanks @maxim-masterov! |
Specify python in ESPResSo. See comment here.