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
If I create a workflow with a job that uses convictional/trigger-workflow-and-wait as a step in a 2 axis matrix, if (even only) one of the matrix jobs fails, all of them show as failed in the workflow.
Additionally, both jobs in the workflow show the work of convictional/trigger-workflow-and-wait for both of the axes of the matrix.
@brianjmurrell it feels a bit more random than that. It should also sometimes succeed even if one fail, as the job will get the last running job of the one its triggering, and most of the times it will just be the last one triggered in the matrix.
The only solution I can think for this is some sleep mechanism for the matrix items, making you run them all in a window bigger than your wait window (which is usually 10 seconds)
If I create a workflow with a job that uses convictional/trigger-workflow-and-wait as a step in a 2 axis matrix, if (even only) one of the matrix jobs fails, all of them show as failed in the workflow.
Additionally, both jobs in the workflow show the work of convictional/trigger-workflow-and-wait for both of the axes of the matrix.
See https://github.com/daos-stack/argobots/actions/runs/3541802004/jobs/5946573980 for an example of this. Only Test RPMs on EL 8 (release/2.2) actually failed. _Test RPMs on EL 8 (master) actually succeeded.
The text was updated successfully, but these errors were encountered: