Closed Bug 587854 Opened 15 years ago Closed 15 years ago

buildbotcustom: When updating sources, discard uncommitted changes

Categories

(Release Engineering :: General, defect, P5)

x86
Linux
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jhopkins, Assigned: jhopkins)

References

Details

Attachments

(2 files, 2 obsolete files)

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'.
Attached patch Proposed patch (obsolete) — Splinter Review
Attachment #466476 - Flags: review?(bhearsum)
Armen, looks like dupe of bug 477095 (which is yours at the moment), but this bug has a patch.
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+
Thank you Rail! Good job Hopkins!
Attachment #466476 - Attachment is obsolete: true
Attachment #466660 - Flags: review?(gozer)
Attachment #466660 - Flags: review?(bhearsum)
Attachment #466660 - Flags: review?(gozer) → review+
Assignee: nobody → john.hopkins
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+
Attachment #466660 - Flags: checked-in+
landed successfully
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
There are quite a few hg updates without -C left, in particular none of the l10n repacks got this.
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 → ---
Put up a patch in bug 588399 to specifically address those problems; not sure if that's everything.
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 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+
bhearsum - right you are. fixed in this patch
Attachment #469489 - Attachment is obsolete: true
Attachment #469489 - Flags: review?(bhearsum)
Sorry, attribution should go to Aki for pointing out flaws in my patch.
patch submitted in buildbotcustom rev 5e28c9b74a4a
Status: REOPENED → RESOLVED
Closed: 15 years ago15 years ago
Resolution: --- → FIXED
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: