You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The reason for this is that when the workflow aborts, it terminates processes in the subprocpool INCLUDING the event handler.
Changing this behaviour will require careful thought as it could trigger events we don't want. E.G. preparing tasks may go into the submit-failed state erroneously.
Can we just leverage the cylc stop --now (but not --now --now) code, for the abort shutdown?
stop -n, --now Shut down without waiting for active tasks to
complete. If this option is specified once, wait for
task event handler, job poll/kill to complete. If this
option is specified more than once, tell the workflow
to terminate immediately.
Abort events take down the scheduler by raising a SchedulerError rather than requesting a shutdown. It's a much more instantaneous stop which also results in a non-zero exit code:
# "cylc play" needs to exit with error status here.
raiseSchedulerError(f'"{abort_conf}" is set')
In the abort case, we want to wait for aborted/timeout handlers, but I guess we might not want to wait for log file retrieval, etc (it could be a really critical shutdown).
The workflow timeout handler is not running when
abort on workflow timeout
is setOriginally posted by @MetRonnie in #5959 (comment)
The text was updated successfully, but these errors were encountered: