-
Notifications
You must be signed in to change notification settings - Fork 355
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
Update pegasus_workflow.py #4936
Update pegasus_workflow.py #4936
Conversation
Is this because pegasus (the full version) is not actually installed on worker nodes? I just want to make sure I understand where this comes up. |
if version.parse(sproc_out) >= version.parse('5.0.4'): | ||
try: | ||
sproc_out = subprocess.check_output(['pegasus-version']).strip() | ||
sproc_out = sproc_out.decode() |
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.
@spxiwh Is there a reason we don't just require >= 5.0.4 anyway?
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.
No real reason why we couldn't do that.
Co-authored-by: Tito Dal Canton <[email protected]>
Yes. The worker package pegasus ships to nodes does not contain a bunch of stuff, and |
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.
Good from my perspective. Thanks!
* Update pegasus_workflow.py * Update pycbc/workflow/pegasus_workflow.py Co-authored-by: Tito Dal Canton <[email protected]> --------- Co-authored-by: Tito Dal Canton <[email protected]>
Bugfix in pegasus_workflow.py
This fix implements a workaround for cases where PyCBC and/or PyGRB workflows have a subworkflow structure that forbid the
pegasus-version
command from being successfully executed on working nodes.This is a: bug fix.
This change affects: the offline search, PyGRB.