CC* factories should halt build if running of client.py fails

RESOLVED FIXED

Status

RESOLVED FIXED
9 years ago
5 years ago

People

(Reporter: standard8, Assigned: standard8)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment, 1 obsolete attachment)

(Assignee)

Description

9 years ago
Created attachment 408389 [details] [diff] [review]
The fix

Currently if client.py fails, the CC* factories in buildbotcustom don't halt the build. This means we go on to compile and possibly run unit tests etc, when really we should just abort as there's no point in doing something else.

Patch attached to set haltOnFailure (only affects comm-central builds).
Attachment #408389 - Flags: review?(gozer)
Attachment #408389 - Flags: review?(bhearsum)
Attachment #408389 - Flags: review?(bhearsum) → review+
Attachment #408389 - Flags: review?(gozer) → review+
Comment on attachment 408389 [details] [diff] [review]
The fix

Good idea, even if sometimes, if client.py fails to pull (instead of failing to clone), the build could have continued. But since that's just hiding hg issues, I think going red right away makes more sense.

Only nit is that since you alter the description/descriptionDone, might as well make it the same everywhere (the last ShellCommand invocation doesn't have them)
(Assignee)

Comment 2

9 years ago
Created attachment 409057 [details] [diff] [review]
The fix v2

Same fix with gozer's comment about adding the description and descriptionDone parameters to the last ShellCommand.
Attachment #408389 - Attachment is obsolete: true
(Assignee)

Comment 3

9 years ago
Checked in: http://hg.mozilla.org/build/buildbotcustom/rev/4314604fdda6

I'll let gozer and KaiRo pick this up when they have time to update buildbotcustom.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
(Assignee)

Updated

9 years ago
Attachment #409057 - Flags: checked-in+
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.