-
Notifications
You must be signed in to change notification settings - Fork 35
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
Flux cleanup #585
Flux cleanup #585
Conversation
Problem: the FLUX ResourceManager docstrings are a bit messy. Clean them up and make them PEP8 compliant.
Problem: the Flux ResourceManager subclass in unnecessarily complicated. Clean it up and simplify the logic for checking down nodes.
Problem: 'bare' try/excepts catch all manner of exceptions and sometimes hide the true source of error. Add better handling for importing and using flux.
Problem: the Flux JobLauncher subclass has some stray variables and unidiomatic Python code. Clean it up.
Problem: the Flux RemoteExec subclass has some duplicated and messy code. Clean it up.
ab2e8ec
to
3b96faf
Compare
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.
Looks great, thanks! I just had a couple of questions inline. I'm new here, but do we have CI that tests this? I imagine this may be difficult or not possible?
We should definitely get CI that tests this if we don't have it! |
Thanks @jameshcorbett. @gonsie, do you know whether our CI tests this? If not, we can at least write up an issue to get it covered at some point. |
Cleaning up some of the Flux code.