Closed
Bug 587854
Opened 15 years ago
Closed 15 years ago
buildbotcustom: When updating sources, discard uncommitted changes
Categories
(Release Engineering :: General, defect, P5)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jhopkins, Assigned: jhopkins)
References
Details
Attachments
(2 files, 2 obsolete files)
2.66 KB,
patch
|
bhearsum
:
review+
gozer
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
2.21 KB,
patch
|
Details | Diff | Splinter Review |
In several of the factories in buildbot custom, "hg update" is run in the default mode which preserves uncommitted modifications. This has caused us issue in the past when making a small change to unbreak a build and that change is forgotten about, thus affecting future build output but never being landed in source control.
Expected:
Uncommitted modifications to a builder source tree are discarded.
Actual:
Uncommitted modifications are preserved across an 'hg update'.
Assignee | ||
Comment 1•15 years ago
|
||
Attachment #466476 -
Flags: review?(bhearsum)
Comment 2•15 years ago
|
||
Armen, looks like dupe of bug 477095 (which is yours at the moment), but this bug has a patch.
Comment 3•15 years ago
|
||
Comment on attachment 466476 [details] [diff] [review]
Proposed patch
Can you get the last few instances, too? Around lines 3510, 3630, and 7090.
It looks like the Mercurial Source step uses --clean when it updates, too, so repos checked out with that should be fine.
Attachment #466476 -
Flags: review?(bhearsum) → review+
Comment 5•15 years ago
|
||
Thank you Rail! Good job Hopkins!
Assignee | ||
Comment 6•15 years ago
|
||
Attachment #466476 -
Attachment is obsolete: true
Attachment #466660 -
Flags: review?(gozer)
Attachment #466660 -
Flags: review?(bhearsum)
Updated•15 years ago
|
Attachment #466660 -
Flags: review?(gozer) → review+
Updated•15 years ago
|
Assignee: nobody → john.hopkins
Comment 7•15 years ago
|
||
Comment on attachment 466660 [details] [diff] [review]
Update to proposed patch with bhearsum's suggestions
Let's land this tomorrow in the downtime.
Attachment #466660 -
Flags: review?(bhearsum) → review+
Updated•15 years ago
|
Attachment #466660 -
Flags: checked-in+
Comment 8•15 years ago
|
||
landed successfully
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Comment 9•15 years ago
|
||
There are quite a few hg updates without -C left, in particular none of the l10n repacks got this.
Comment 10•15 years ago
|
||
Re-opening based on Axel's comment. John, do you want to fix those up?
Assignee: john.hopkins → nobody
Status: RESOLVED → REOPENED
Priority: -- → P5
Resolution: FIXED → ---
Comment 11•15 years ago
|
||
Put up a patch in bug 588399 to specifically address those problems; not sure if that's everything.
Assignee | ||
Comment 12•15 years ago
|
||
Thanks for the patch, Aki. I've found two more instances which should be all that remains to resolve this bug.
Assignee: nobody → john.hopkins
Attachment #469489 -
Flags: review?(bhearsum)
Attachment #469489 -
Flags: review?(aki)
Comment 13•15 years ago
|
||
Comment on attachment 469489 [details] [diff] [review]
Two additional instances caught are added to Aki's patch
>+ 'hg -C -R '+self.origSrcDir+' up ;'+
afaict, hg -C update will error out; the -C needs to come after the up/update.
so |'hg -R '+self.origSrcDir+' up -C ;'+| seems correct.
>+ 'hg -C -R '+locale+' up -r '+self.l10nTag+' ; '
here too.
r=me with those changes.
Attachment #469489 -
Flags: review?(aki) → review+
Assignee | ||
Comment 14•15 years ago
|
||
bhearsum - right you are. fixed in this patch
Attachment #469489 -
Attachment is obsolete: true
Attachment #469489 -
Flags: review?(bhearsum)
Assignee | ||
Comment 15•15 years ago
|
||
Sorry, attribution should go to Aki for pointing out flaws in my patch.
Assignee | ||
Comment 16•15 years ago
|
||
patch submitted in buildbotcustom rev 5e28c9b74a4a
Status: REOPENED → RESOLVED
Closed: 15 years ago → 15 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
•