Closed
Bug 466998
Opened 17 years ago
Closed 17 years ago
ReleaseUpdatesFactory 'cvs diff' step (validly) returns 1, turns step red
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: bhearsum)
References
Details
(Whiteboard: [hg-automation])
Attachments
(1 file)
3.88 KB,
patch
|
coop
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
'cvs diff' returns 1 when there's differences between the local copy and the checked-in version. Buildbot needs to be taught to ignore that return code.
Assignee | ||
Updated•17 years ago
|
Whiteboard: [hg-automation]
Assignee | ||
Comment 1•17 years ago
|
||
Alright, so I've modified TinderboxShellCommand a little bit to make accept a list of ignorable exit codes. This lets us ignore the valid exit code of '1' and still catch errors such as a file not existing, or no changes being made at all (which is an error in this case!).
This patch also updates L10nVerifyMetaDiff to subclass from TinderboxShellCommand to take advantage of the same thing. Note that this step will sometimes show no diff at all - which is entirely valid, so the ignorable codes here are both 0 and 1.
Attachment #350342 -
Flags: review?(ccooper)
Updated•17 years ago
|
Attachment #350342 -
Flags: review?(ccooper) → review+
Assignee | ||
Updated•17 years ago
|
Attachment #350342 -
Flags: checked‑in+
Assignee | ||
Comment 2•17 years ago
|
||
Comment on attachment 350342 [details] [diff] [review]
make 'cvs diff' step ignore exit code 1
Checking in process/factory.py;
/cvsroot/mozilla/tools/buildbotcustom/process/factory.py,v <-- factory.py
new revision: 1.46; previous revision: 1.45
done
Checking in steps/misc.py;
/cvsroot/mozilla/tools/buildbotcustom/steps/misc.py,v <-- misc.py
new revision: 1.8; previous revision: 1.7
done
Checking in steps/release.py;
/cvsroot/mozilla/tools/buildbotcustom/steps/release.py,v <-- release.py
new revision: 1.3; previous revision: 1.2
done
Assignee | ||
Updated•17 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•