Closed
Bug 806158
Opened 12 years ago
Closed 12 years ago
graphserver posts for builds should not haltOnFailure
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: philor, Assigned: massimo)
Details
(Whiteboard: [simple])
Attachments
(1 file)
|
1.32 KB,
patch
|
catlee
:
review+
catlee
:
checked-in+
|
Details | Diff | Splinter Review |
If a talos job fails to post to graphserver, sure, that's it, it's dead and worthless and we should just give up on it, and if graphserver's down like it is right now, we should retrigger them all when it comes back. If a build fails to post to graphserver, it's not dead and worthless, it's just going to fail to graph some numbers that nobody is really interested in, and we should not have to retrigger it to get past the graphserver post and on to the upload and sendchange that are what we really want out of the build.
|
||
Comment 1•12 years ago
|
||
Probably just need to set haltOnFailure and flunkOnFailure to False here: http://hg.mozilla.org/build/buildbotcustom/file/1ca6bf1f11ec/process/factory.py#l1273
Whiteboard: [simple]
|
Assignee | |
Updated•12 years ago
|
Assignee: nobody → mgervasini
|
|
Assignee | |
Comment 2•12 years ago
|
||
Attachment #677761 -
Flags: review?(catlee)
|
|
||
Updated•12 years ago
|
Attachment #677761 -
Flags: review?(catlee) → review+
|
|
||
Updated•12 years ago
|
Attachment #677761 -
Flags: checked-in+
|
||
Comment 3•12 years ago
|
||
In production
|
|
||
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
|
||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
|
|
||
Updated•6 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•