-
Notifications
You must be signed in to change notification settings - Fork 26
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
Phases complete and shown as successful even if a task fails #1077
Comments
This is the current behavior: relman, sheriffs, and releng watch the graphs to make sure they go green. So one way would be to require addons reviews/signoffs to include a green task group check. We could add a shipit task in each phase that marks the phase as completed, but a) there are some cases where non-blocking leaf nodes fail in the Firefox release graph and we decide that that's ok, so we can't make it a hard failure; and b) we'll have to slot that into Releng's current priorities. |
Thank you. I believe blocking would be ideal for add-ons. If that is not feasible or takes a long time, could we start by non-blocking, but showing something other than the blue checkmark on shipit? This would help users to immediately see if something requires their attention, without having to (remember to) inspect the tasks every time. |
#1087 makes is it so the ShipIt phase progress accounts for the state of tasks in the phase's task group. Making it non-blocking so Firefox releases can still be signed off if there's some failing tasks. We can also block on failed tasks for add-ons and allow sign offs with failed task group tasks for Firefox. |
Recently, I triggered the "Ship" phase for firefox-translations-1.1.2-build which completed according to shipit:
However, looking at the task group in task cluster, one task has failed:
Similarly, the a build for searchengine-devtools failed (https://firefox-ci-tc.services.mozilla.com/tasks/groups/SzR0NU1xThGCnCKdi2Datw), but shipit showed completed and even allowed me to sign off on it. I have canceled that build in the meantime. The same goes for a recent remote-settings-devtools build
In the task-group, the linter task failed:
The text was updated successfully, but these errors were encountered: