Closed
Bug 425204
Opened 17 years ago
Closed 17 years ago
fix formatting differences between our tree and upstream buildbot
Categories
(Release Engineering :: General, defect, P2)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: bhearsum)
References
Details
Attachments
(1 file)
1.94 KB,
patch
|
rcampbell
:
review+
|
Details | Diff | Splinter Review |
With the Buildbot 0.7.7 release looming I did a local test import of the current trunk. Everything was fine except for a formatting difference in tinderbox.py. There's also a couple of patches that apparently didn't get upstream. I've filed those in http://buildbot.net/trac/ticket/214 and http://buildbot.net/trac/ticket/213. I'm attaching a patch to change our formatting to match the the Buildbot trunk. Once this is landed and Buildbot tickets 214 an 213 are landed we should be able to import 0.7.7 conflict-free.
Attachment #311814 -
Flags: review?(rcampbell)
Assignee | ||
Updated•17 years ago
|
Priority: -- → P2
Comment 1•17 years ago
|
||
Comment on attachment 311814 [details] [diff] [review]
[checked in] formatting parity with upstream buildbot
nice'n'easy
Attachment #311814 -
Flags: review?(rcampbell) → review+
Assignee | ||
Updated•17 years ago
|
Blocks: buildbot-0.7.7
Assignee | ||
Comment 2•17 years ago
|
||
Comment on attachment 311814 [details] [diff] [review]
[checked in] formatting parity with upstream buildbot
Checking in buildbot/status/tinderbox.py;
/cvsroot/mozilla/tools/buildbot/buildbot/status/tinderbox.py,v <-- tinderbox.py
new revision: 1.8.2.1; previous revision: 1.8
done
landed on BUILDBOT_0_7_6_BRANCH
Attachment #311814 -
Attachment description: formatting parity with upstream buildbot → [checked in] formatting parity with upstream buildbot
Assignee | ||
Updated•17 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Updated•17 years ago
|
Component: Release Engineering: Talos → Release Engineering
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
•