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
wpbonelli opened this issue
Jan 28, 2022
· 1 comment
Assignees
Labels
bugSomething isn't workingpriorityShould be resolved first, if possiblepythonPull requests that update Python codequestionFurther information is requested
Currently a task is considered to have succeeded if the corresponding scheduler job runs to completion without timing or erroring out. This includes tasks which expect outputs but fail to produce them. This is misleading and confusing- if a job is expected to produce output files, we should mark it failed if it does not.
Are there any other similar cases to consider?
The text was updated successfully, but these errors were encountered:
bugSomething isn't workingpriorityShould be resolved first, if possiblepythonPull requests that update Python codequestionFurther information is requested
Currently a task is considered to have succeeded if the corresponding scheduler job runs to completion without timing or erroring out. This includes tasks which expect outputs but fail to produce them. This is misleading and confusing- if a job is expected to produce output files, we should mark it failed if it does not.
Are there any other similar cases to consider?
The text was updated successfully, but these errors were encountered: