-
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
cylc 6: start-up task back-compat problem #1008
Milestone
Comments
benfitzpatrick
added a commit
to benfitzpatrick/cylc
that referenced
this issue
Jul 21, 2014
benfitzpatrick
added a commit
to benfitzpatrick/cylc
that referenced
this issue
Jul 24, 2014
benfitzpatrick
added a commit
to benfitzpatrick/cylc
that referenced
this issue
Jul 28, 2014
benfitzpatrick
added a commit
to benfitzpatrick/cylc
that referenced
this issue
Jul 28, 2014
benfitzpatrick
added a commit
to benfitzpatrick/cylc
that referenced
this issue
Jul 28, 2014
benfitzpatrick
added a commit
to benfitzpatrick/cylc
that referenced
this issue
Jul 28, 2014
The run time behaviour here is now fixed, but graphing is still broken, see: #1026 (comment) |
hjoliver
added a commit
that referenced
this issue
Jul 30, 2014
…dep-tweak #1008: more minimal start-up dependencies
benfitzpatrick
added a commit
to benfitzpatrick/cylc
that referenced
this issue
Aug 18, 2014
hjoliver
added a commit
that referenced
this issue
Aug 18, 2014
#1008: fix start-up graphing in simplest case
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If
prep
is an old-style start-up task,This gets auto-upgraded to
prep[^] => X
for the first four cycle points, then justX
for the general recurrence. Which is not the same as in cylc-5, where the first instance ofX
triggers offprep
, but all subsequent instances do not (mad but true).@benfitzpatrick - is it easy for you to just apply the auto graph upgrade to the first cycle point in a list, where start-up and cold-start tasks are involved? (I'm sure it is easy as stated, but are there consequences for other suites...). Otherwise "wontfix" is probably fine as I doubt this is of much consequence in reality.
The text was updated successfully, but these errors were encountered: