-
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
Terminology: suite to workflow #4174
Conversation
All tests passing locally. |
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 have worked my way through the bulk of this PR.
Couple of comments.
All tests pass for me locally. I have also read through code changes.
Will re-review when the
TODO: restore CYLC_SUITE_* job environment variables for back-compat
has been completed.
This change will break ui so will wait on giving explicit approval before a companion pr for cylc-uiserver is also approved.
Thanks @datamel, I'm sure that was mildly painful! |
Should be good to go now. No need to merge for beta-1 release though. |
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 have reviewed the final files that I didn't get to yesterday...
!!!!
A couple of points....
- (Minor) On occasion you have replaced
suite server program
withscheduler
, did you want to sed workflow server program and change them all to scheduler for consistency? - (Minor)
etc/bin/run-functional-tests
has a couple of workflows that should be suites. - (Possibly more major) I have checkout out sibling PRs and get errors when my run directory contains a contact file with old fields e.g CYLC_SUITE_UUID.. this returns traceback to the user
Maybe we want some back compatibility, since users may encounter this problem?
Compatibility for cylc review was also raised by @dpmatthews, @wxtim has added this to his to do list.
Good points @datamel, I'll address them soon... |
69fc60c
to
d886b46
Compare
d886b46
to
ff94ee2
Compare
(closed and reopened to trigger Actions) |
@datamel -
Last commit fixes this. (It fixes |
I think the test failures are spurious - something weird just happened (see comment on Element) ... but I'll come back to check later. |
Tests passing 🎉 |
Co-authored-by: Ronnie Dutta <[email protected]>
Co-authored-by: Ronnie Dutta <[email protected]>
Thanks, excellent reviewing! 💐 |
1d40697
to
4833d6c
Compare
0e26b28
to
0d574b7
Compare
0d574b7
to
6e718d3
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.
I can confirm the issue that resulted in traceback on ui-server has been fixed.
Approved.
Couldn't find any words in the English language which match that pattern, gonna have to be more specific. |
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.
Well that was fun!
I think we need to keep the "suite" fields we provide to suiteworkflow/task event scripts (unless there's some clever logic handling that I didn't spot).
6ced750
to
697c407
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.
👍
Brace for conflicts, it's going in! |
This is a
smalllarge-but-trivial change with no associated Issue (but discussed with the team!)*suite*
filenames as*workflow*
suite.rc
CYLC_SUITE_*
job environment variables for back-compatNote:
Requirements check-list
CONTRIBUTING.md
and added my name as a Code Contributor.