-
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
:expire trigger broken #5364
Comments
Per #5361 - we also need to consider required outputs of expired tasks. |
Oops:
|
Have reproduced with this
In Cylc 7, |
@MetRonnie - have you started working on this? If not, I can post a fix pretty quickly. |
I'll take over this one, it appears @MetRonnie is not working on it... |
Have had an issue reported where a task expired DURING its second try leaving behind a job in the submitted state which subsequently could not be killed (because the task isn't in the pool). Possibly related? |
Not related to the "expire trigger" as such, but a good point to note. We should not allow an already-active task to expire. |
By broken I mean, it has no effect.
When implementing the spawn-on-demand scheduler, I think I must have forgotten about the
:expired
trigger, and hence removed expired tasks before triggering on that "output" (because an expired task does not have any other outputs).The text was updated successfully, but these errors were encountered: