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)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: standard8, Assigned: standard8)

Details

Attachments

(1 file, 1 obsolete file)

Attached patch The fix (obsolete) — 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)
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)
Attached patch The fix v2Splinter Review
Same fix with gozer's comment about adding the description and descriptionDone parameters to the last ShellCommand.
Attachment #408389 - Attachment is obsolete: true
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
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.

Attachment

General

Created:
Updated:
Size: