Skip to content

Remove continue-on-error so job failures fail the workflow. #1085

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

Merged

Conversation

OhmSpectator
Copy link
Member

The smoke, storage and eve-upgrade jobs no longer ignore step errors, ensuring any failing job marks the whole workflow as failed. To keep all matrix permutations running, each job’s strategy now explicitly sets fail-fast: false. This preserves full test coverage without cancelling siblings early while still surfacing problems in red at the workflow level.

The smoke, storage and eve-upgrade jobs no longer ignore step errors,
ensuring any failing job marks the whole workflow as failed. To keep all
matrix permutations running, each job’s strategy now explicitly sets
fail-fast: false. This preserves full test coverage without cancelling
siblings early while still surfacing problems in red at the workflow
level.

Signed-off-by: Nikolay Martyanov <[email protected]>
@OhmSpectator OhmSpectator force-pushed the fix/do-not-allow-error-in-steps branch from 96aa8b3 to 2561237 Compare July 22, 2025 08:19
@uncleDecart
Copy link
Member

The initial idea of that was that it takes us multiple runs to make them work, do you think that eden tests are stable enough to enable that?

@OhmSpectator
Copy link
Member Author

It does not affect the Eden runs much. It still allows tests to continue if any job fails. It just doesn't mark a job as successful if one of its steps fails. We had used the wrong approach to preserve the matrix functionality.

@OhmSpectator OhmSpectator merged commit b049c93 into lf-edge:master Jul 22, 2025
29 of 32 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants