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

python: flux-sched doesn't configure on CORAL #636

Closed
dongahn opened this issue Apr 1, 2020 · 5 comments
Closed

python: flux-sched doesn't configure on CORAL #636

dongahn opened this issue Apr 1, 2020 · 5 comments

Comments

@dongahn
Copy link
Member

dongahn commented Apr 1, 2020

With TCE:

checking whether yaml-cpp has YAML::Node::Mark... no
checking for boostlib >= 1.53.0 (105300)... yes
checking for buggy boostlib versions (105400-105800)... no
checking whether the Boost::System library is available... yes
checking for exit in -lboost_system... yes
checking whether the Boost::Filesystem library is available... yes
checking for exit in -lboost_filesystem... yes
checking whether the Boost::Graph library is available... yes
checking for exit in -lboost_graph... yes
checking whether the Boost::Regex library is available... yes
checking for exit in -lboost_regex-mt... yes
checking for readline in -lreadline... yes
checking for python3.7... no
configure: error: Cannot find python3.7 in your system path

Don't know if python3.6 would satisfy the python requirement of flux-sched. @SteVwonder: are we using unique features from python3.7 within flux-sched?

@dongahn
Copy link
Member Author

dongahn commented Apr 1, 2020

module load python/3.7.2 seems to do things better. Let me reconfig and rebuild both flux-core and flux-sched with this.

@dongahn
Copy link
Member Author

dongahn commented Apr 1, 2020

OK. Turns out module load python/3.7.2 was the key.

@dongahn dongahn closed this as completed Apr 1, 2020
@SteVwonder
Copy link
Member

Hmm. That's an interesting behavior. The flux-sched configure is still set to check for 2.7+. Did you happen to configure flux-core against py3.7? My suspicion is that flux-sched is attempting to configuring itself against the same python that core was configured against (which is probably the behavior that we want to enforce.....error message could be better though).

@dongahn
Copy link
Member Author

dongahn commented Apr 1, 2020

Did you happen to configure flux-core against py3.7?

No when I tested this, I configured flux-core against py3.6...

My suspicion is that flux-sched is attempting to configuring itself against the same python that core was configured against (which is probably the behavior that we want to enforce.....error message could be better though).

How does flux-sched figure this out though?

@SteVwonder
Copy link
Member

No when I tested this, I configured flux-core against py3.6...

Do you know which py3.6 interpreter you were using? I'd like to try and reproduce this. In flux-framework/flux-core#2881, it looks like the system-installed 3.6 failed for you. Did you use a python 3.6 in your home directory?

How does flux-sched figure this out though?

This little bit of m4/python/flux magic (credit goes to @grondo):

FLUX_PYTHON_VERSION=$($FLUX python -c 'import sys; print(".".join(map(str, sys.version_info[[:2]])))')

So to be precise, flux-sched tries to configure itself with the same python version as flux-core. It doesn't enforce the exact same interpreter path.

@dongahn dongahn changed the title python: flux-shed doesn't configure on CORAL python: flux-sched doesn't configure on CORAL Aug 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants