Closed
Bug 524461
Opened 15 years ago
Closed 15 years ago
CC* factories should halt build if running of client.py fails
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: standard8, Assigned: standard8)
Details
Attachments
(1 file, 1 obsolete file)
1.54 KB,
patch
|
standard8
:
checked-in+
|
Details | Diff | Splinter Review |
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)
Updated•15 years ago
|
Attachment #408389 -
Flags: review?(bhearsum) → review+
Updated•15 years ago
|
Attachment #408389 -
Flags: review?(gozer) → review+
Comment 1•15 years ago
|
||
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•15 years ago
|
||
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•15 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
Closed: 15 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•15 years ago
|
Attachment #409057 -
Flags: checked-in+
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•