Closed Bug 806158 Opened 10 years ago Closed 10 years ago

graphserver posts for builds should not haltOnFailure

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: philor, Assigned: massimo)

Details

(Whiteboard: [simple])

Attachments

(1 file)

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.
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: nobody → mgervasini
Attachment #677761 - Flags: review?(catlee) → review+
Attachment #677761 - Flags: checked-in+
In production
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.