Skip to content
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

PythonPackage is not compatible with --sanity-check-only #2745

Closed
boegel opened this issue Jun 9, 2022 · 1 comment · Fixed by #2828
Closed

PythonPackage is not compatible with --sanity-check-only #2745

boegel opened this issue Jun 9, 2022 · 1 comment · Fixed by #2828
Milestone

Comments

@boegel
Copy link
Member

boegel commented Jun 9, 2022

Using --sanity-check-only on something that was installed with the PythonPackage (or PythonBundle, or a derivative) easyblock fails with:

== FAILED: Installation ended unsuccessfully (build directory: /tmp/easybuild_build/pygmo/2.16.1/foss-2020b): build failed (first 300 chars): cmd "pip --version" exited with exit code 127 and output:
/bin/bash: pip: command not found
 (took 0 secs)

The problem is that the module (which is already installed) only gets loaded later, when the parent sanity_check_step is being called.

@boegel boegel added this to the next release (4.5.6?) milestone Jun 9, 2022
boegel added a commit to boegel/easybuild-easyblocks that referenced this issue Sep 26, 2022
boegel added a commit to boegel/easybuild-easyblocks that referenced this issue Sep 26, 2022
boegel added a commit to boegel/easybuild-easyblocks that referenced this issue Sep 26, 2022
boegel added a commit to boegel/easybuild-easyblocks that referenced this issue Nov 16, 2022
@mboisson
Copy link
Contributor

This caused a regression with multi_deps. See the linked PR to fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants