-
Notifications
You must be signed in to change notification settings - Fork 53
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
Remove port file related logic #2109
Conversation
@@ -204,7 +204,7 @@ class SuiteStillRunningError(Exception): | |||
FMT_HEAD = "Suite \"%(suite_name)s\" has running processes on:" | |||
FMT_BODY_1 = " %(host_name)s" | |||
FMT_BODY_M = "\n %(host_name)s" | |||
FMT_TAIL = "\nTry \"rose suite-shutdown --name=%(suite_name)s\" first?" | |||
FMT_TAIL = "\nTry \"cylc stop '%(suite_name)s'\" first?" |
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.
Is there a reason for switching this? i.e. Rose to recommend running a Cylc command (I mean I guess in practice people almost always have Rose + Cylc), just wondered.
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.
rose suite-shutdown
was an essential command for picking the correct suite host for the cylc stop
command. It became unnecessary since cylc/cylc-flow#1705, and I would like to encourage users to call cylc stop
directly to reduce overhead.
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.
Are any of the rose test-battery tests known to be problematic? rose-bush/06-host-port.t
is failing on my machine. (Against cylc master) Although it's fine in Travis...
@matthewrmshin also |
Trust the cylc 7 contact file as an indicator that a suite is running.
cede019
to
125aed2
Compare
The tests are both OK in my environment, (but I guess it is worth checking what is causing the failure in your environment). Neither tests should be related to this change. |
Trust the cylc 7 contact file as an indicator that a suite is running.