-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[prebuilds] Introduce 'failed' state for prebuilds #8602
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
Conversation
2d0a277
to
b8f3157
Compare
/werft run 👍 started the job as gitpod-build-se-prebuilds-failed.2 |
b8f3157
to
6dcafb8
Compare
/werft run 👍 started the job as gitpod-build-se-prebuilds-failed.4 |
Codecov Report
@@ Coverage Diff @@
## main #8602 +/- ##
===========================================
- Coverage 28.98% 11.17% -17.81%
===========================================
Files 150 18 -132
Lines 23118 993 -22125
===========================================
- Hits 6700 111 -6589
+ Misses 15808 880 -14928
+ Partials 610 2 -608
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
6dcafb8
to
2d8d852
Compare
The error handling makes sense and the changes look good. I'm just not sure about the presentation on the dashboard, it seems to be the same as the "headless task failed" case. Could we render the "system error" case differently? |
Distinguish between failed tasks but finished prebuilds and fully failed prebuilds (no snapshot) fixes #8592
2d8d852
to
4769e41
Compare
/werft run 👍 started the job as gitpod-build-se-prebuilds-failed.7 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
💯
Description
This PR introduces a "failure" state for prebuilds that have entirely failed to finish.
This is to distinguish them from failed tasks but finished rebuilds.
Related Issue(s)
fixes #8592
Release Notes