Closed
Bug 1212318
Opened 9 years ago
Closed 8 years ago
[release-promotion] L10N repacks should not automatically rerun on failure
Categories
(Release Engineering :: Release Automation: Other, defect)
Release Engineering
Release Automation: Other
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: rail, Unassigned)
References
Details
See https://tools.taskcluster.net/task-graph-inspector/#UVpyEvsPQjKFpPRPzmc7vQ/5YiVueXPShOFZFpbjWdCUw/3 I'm not sure if this is buildbot or the bridge...
|
Reporter | |
Updated•9 years ago
|
Severity: normal → major
|
|
Reporter | |
Comment 1•9 years ago
|
||
<mcote> buildbot-bridge looks like it's building up unacked messages <mcote> sounds like they're being received but maybe something is crashing before they're acked <rail-away> hmm, that may explain retries even though it shouldn't retry
|
|
Reporter | |
Comment 2•9 years ago
|
||
Probably it's TC, the same applies for the source task: https://tools.taskcluster.net/task-graph-inspector/#hpI68-8-RJeeSa4C-M-04Q/MSlArxPDQZiECS2lMLknEg/5
|
|
Reporter | |
Comment 5•8 years ago
|
||
I have time to look at BBB today and looks like it respects the buildbot exit codes. The only place where it reschedules a task is https://github.com/mozilla/buildbot-bridge/blob/2c38c205635ba018598f412e288f7b10a3201100/bbb/services.py#L191-L203
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•