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
It would be nice if in our Argo workflows we could mark steps as failed but not have them block dependent execution.
An example would be lint tests. Even if lint tests fail we'd like the rest of the steps in the DAG to execute.
This might just be a function of the fact that we aren't using Argo's newly added DAG functionality. So in our case the Setup cluster step depends on the lint step. But maybe if we change that to be a true DAG so the E2E test no longer depends on the lint step then lint failures won't cause the E2E test to fail.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
It would be nice if in our Argo workflows we could mark steps as failed but not have them block dependent execution.
An example would be lint tests. Even if lint tests fail we'd like the rest of the steps in the DAG to execute.
This might just be a function of the fact that we aren't using Argo's newly added DAG functionality. So in our case the Setup cluster step depends on the lint step. But maybe if we change that to be a true DAG so the E2E test no longer depends on the lint step then lint failures won't cause the E2E test to fail.
The text was updated successfully, but these errors were encountered: