-
Notifications
You must be signed in to change notification settings - Fork 94
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
Fix failure to clean on remote host with leftover contact file #4978
Conversation
and not (path / 'workflow').exists() | ||
and not (path / 'scheduler').exists() |
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.
Unrelated change but spotted this leftover today
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.
Happy with this - add a changelog entry before merging.
Dang, just realised this approach is flawed - if there are configured remote run hosts, it will allow |
Changed approach, relying on the fact that the workflow DB only exists on the scheduler host. |
Follow-up to cylc#4836
The codecov upload is too flaky
Re-done as per Oliver's suggestion |
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.
(A very quick review but LGTM; I haven't tested it).
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.
I'm OK with this. @oliver-sanders - do you want to do a final check?
LGTM |
This is a small change with no associated Issue.
From Teams:
Solution
If there us a leftover contact file when doingcylc clean
, if the host field gives a host that is not the local host, it means we are doing re-invokedcylc clean --local-only
on the remote host and we should not check if the scheduler process is still running (it can't be).The workflow DB only exists on the scheduler host. So if we are doing
cylc clean --local-only
and there is a leftover contact file but no DB, it probably means this iscylc clean
being re-invoked on a remote host and we can ignore the contact.Even if the fix gets hit when someone genuinely someone runs
cylc clean --local-only
on the scheduler host, it shouldn't matter.Requirements check-list
CONTRIBUTING.md
and added my name as a Code Contributor.setup.cfg
andconda-environment.yml
.