Skip Mode #6039
Open
Skip Mode #6039
+2,868
−859
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wxtim
force-pushed
the
feature.skip_mode
branch
2 times, most recently
from
b43d296
to
d26c315
Compare
wxtim
force-pushed
the
feature.skip_mode
branch
from
d378e3a
to
e9c2e25
Compare
wxtim
requested review from
oliver-sanders,
markgrahamdawson and
MetRonnie
and removed request for
markgrahamdawson
MetRonnie
reviewed
Apr 23, 2024
wxtim
force-pushed
the
feature.skip_mode
branch
4 times, most recently
from
3d002ee
to
dd0a9fc
Compare
MetRonnie
reviewed
May 8, 2024
wxtim
force-pushed
the
feature.skip_mode
branch
3 times, most recently
from
0d42eab
to
c37ef72
Compare
wxtim
force-pushed
the
feature.skip_mode
branch
2 times, most recently
from
3839a8a
to
d7ee653
Compare
MetRonnie
reviewed
May 20, 2024
values for ___retry_delays, as the lack of these causes failure on task retry or re-triggering.
Co-authored-by: Ronnie Dutta <61982285+MetRonnie@users.noreply.github.com>
* Rename generalized run mode validation function to only checking skip mode validation.
Co-authored-by: Ronnie Dutta <61982285+MetRonnie@users.noreply.github.com>
Co-authored-by: Ronnie Dutta <61982285+MetRonnie@users.noreply.github.com>
wxtim
force-pushed
the
feature.skip_mode
branch
from
a78b95d
to
0c5e639
Compare
MetRonnie
reviewed
Oct 31, 2024
cylc/flow/task_outputs.py
Outdated
Comment on lines
637
to
638
| exclude: Exclude one possible required message, allowing | ||
| specification of all required outputs if succeeded or failed. |
There was a problem hiding this comment.
Could this be explained better? I am not sure what this means (though judinging from the tests it is not as simple as just excluding the specified output from the return value, which was my first impression)
wxtim
force-pushed
the
feature.skip_mode
branch
from
aeca3e4
to
2aa3f1c
Compare
wxtim
force-pushed
the
feature.skip_mode
branch
from
2aa3f1c
to
51f6585
Compare
8 tasks
MetRonnie
reviewed
Nov 11, 2024
Comment on lines
+79
to
+80
| 'disable task event handlers': | ||
| rtconfig['simulation']['disable task event handlers'], |
There was a problem hiding this comment.
Does this need to be set? In simulation mode all tasks event handlers are disabled anyway?
Comment on lines
+60
to
+61
| 'disable task event handlers': | ||
| rtconfig['skip']['disable task event handlers'], |
There was a problem hiding this comment.
Actually, why add this to the platform dict instead of just accessing it on itask.tdef.rtconfig['simulation']['disable task event handlers']? (Or maybe setting it on itask.mode_settings for shorter access)
(disable task event handlers is not a settable platform configuration in global.cylc so this is slightly confusing)
| name, rtcfg, self.run_mode(), self.start_point, | ||
| name, | ||
| rtcfg, | ||
| RunMode.get(self.options), |
There was a problem hiding this comment.
A quick search suggests to me that TaskDef.run_mode is no longer used anywhere
Co-authored-by: Ronnie Dutta <61982285+MetRonnie@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #5641 (also fixes #5975, and fixes #5820 )
Skip Mode Proposal Doc
This branch includes (marked against skip mode proposal):
[runtime][<namespace>]run mode.a. Broadcast can change
run modefor future task job submissions.b. Cylc Validate and lint will warn about the setting not being live.
cylc set --out skipsets outputs from skip mode.run mode = skiprespectsis_heldflag.Extras
7. Run Mode is available as an task attribute in the UI
8. When tasks are run in skip mode, the prerequisites which correspond to the outputs they generate should be marked as satisfied by skip mode rather than satisfied naturally for provenance reasons. For the purpose of cylc remove logic, satisfied by skip mode should be treated the same as satisfied naturally.
There are two extensions, which I haven't dealt with yet, because I want to ensure that the basic functionality works, and move to the substantial documentation PR which need follow this.
Check List
CONTRIBUTING.mdand added my name as a Code Contributor.setup.cfg(andconda-environment.ymlif present).CHANGES.mdentry included if this is a change that can affect users