Closed
Bug 966523
Opened 10 years ago
Closed 10 years ago
Need to update mozilla-inbound pushlog to include a push that I interrupted (which made it into m-i hg log, but not pushlog)
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: dholbert, Unassigned)
Details
A little while back, I pushed to mozilla-inbound, and then did "Ctrl+c" shortly after pushing: { [dholbert@indigo:/scratch/work/builds/mozilla-inbound/mozilla]$ hg push pushing to ssh://hg.mozilla.org/integration/mozilla-inbound/ searching for changes h^Cinterrupted! remote: adding changesets remote: adding manifests remote: adding file changes remote: added 1 changesets with 1 changes to 1 files [dholbert@indigo:/scratch/work/builds/mozilla-inbound/mozilla]$ } and apparently that push made it into mozilla-inbound but not into the pushlog. The cset in question is http://hg.mozilla.org/integration/mozilla-inbound/rev/a4bd676baee6 I'm told in #releng that we need to insert a dummy entry into the pushlog. Filing this bug on that.
Reporter | ||
Comment 1•10 years ago
|
||
If it helps: the timestamp in the cset itself (Fri Jan 31 14:54:08 2014 -0800) should be a suitable time for the dummy pushlog-entry. That time is very close to when I pushed, and it fits in between the pushlog timestamps on the push before/after (which were at 14:52 and 14:56, respectively).
Comment 2•10 years ago
|
||
Given this is a comment-only change and is DONTBUILD, we're not going to risk pushlogdb surgery on a Friday night to fix this. We're getting builds on subsequent pushes, so automation seems oblivious to the omission.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Reporter | ||
Comment 3•10 years ago
|
||
I filed bug 966545 on finding ways to prevent this sort of thing from happening in the future.
Updated•6 years ago
|
Product: Release Engineering → Infrastructure & Operations
Updated•4 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•