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
For some dynamic workflows, the number of steps/jobs is not known in advance. Some steps/jobs are created by the workflow say in scatter-gather situations as the workflow is running.This leads to situations such as:
status=finished, steps=21/18
which may be hard to interpret by the users.
We could:
document this better
or change the way how the progress is calculated
The former is easy, the latter is the focus of this issue.
Basically, we have to be ready that the total number of steps for a workflow can change as the workflow runs.
For some dynamic workflows, the number of steps/jobs is not known in advance. Some steps/jobs are created by the workflow say in scatter-gather situations as the workflow is running.This leads to situations such as:
which may be hard to interpret by the users.
We could:
The former is easy, the latter is the focus of this issue.
Basically, we have to be ready that the total number of steps for a workflow can change as the workflow runs.
See the past discussion in reanahub/reana-workflow-engine-serial#14 about
N1 planned, N2 succeeded, N3 failed, N4 submitted, N total jobs for a workflow.
We can revive the issue based on those musings.
The text was updated successfully, but these errors were encountered: