Skip to content
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 reload-alteration of a reload-removed then reload-added task #1826

Merged

Conversation

benfitzpatrick
Copy link
Contributor

This closes #1759. A task that became a reload orphan always stayed an orphan in future reloads and couldn't be changed via reload.

It also fixes a small issue I found when debugging - reload in itself doesn't trigger a state summary update. This isn't always necessary (e.g. when just altering the runtime) but seems like a good idea.

@arjclark, @hjoliver please review.

@benfitzpatrick benfitzpatrick added this to the next-release milestone May 3, 2016
@arjclark arjclark modified the milestones: soon, next-release May 3, 2016
@hjoliver hjoliver modified the milestones: next release, soon May 4, 2016
@hjoliver hjoliver force-pushed the master branch 3 times, most recently from 17fe934 to 3bdb067 Compare May 5, 2016 01:37
@arjclark
Copy link
Contributor

arjclark commented May 6, 2016

Looks ok to me and test-battery passing in my environment.

Over to you @hjoliver - please double check I haven't missed any unforseen consequence from this as I'm generally scared of reloads as it is 😬

@arjclark arjclark assigned hjoliver and unassigned arjclark May 9, 2016
@hjoliver
Copy link
Member

All good here, and I don't think there will be any unforeseen consequences!

@hjoliver hjoliver merged commit b3ca94f into cylc:master May 11, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

cylc reload: deleted then re-added task not affected by runtime reloads
3 participants