All users were logged out of Bugzilla on October 13th, 2018
14.45 KB, text/plain
1.28 KB, text/plain
http://hg.mozilla.org/releases/l10n/mozilla-aurora/da/pushloghtml looks like the single head hook isn't on on the l10n/mozilla-aurora repos. http://hg.mozilla.org/releases/l10n/mozilla-aurora/da/pushloghtml?changeset=6c6a233d6f6e maps to http://hg.mozilla.org/releases/l10n/mozilla-aurora/da/graph/173 which is resolved to a single head graph in a different push, http://hg.mozilla.org/releases/l10n/mozilla-aurora/da/pushloghtml?changeset=56c62143221b, leading to http://hg.mozilla.org/releases/l10n/mozilla-aurora/da/graph/174 CCing jepser and sskroeder who pushed. This also invalidates quite a few assumptions going in to how we're doing builds and releases.
Yes, Søren forgot to update before he committed, resulting in two heads in the repository on hg.mozilla.org. I merged them afterwards.
Created attachment 532277 [details] dump from terminal when "illegal push" had been made (350 lines)
As Jesper and Søren are confused by the jargon in this bug: There's a mercurial hook available on hg.mozilla.org that checks if you're creating anymore than one head on any branch, nicknamed single-head. When that hook is on, you can do whatever you want, you won't be able to push a second head on default, including the `hg push -f` that Søren did. That hook is supposed to be on, and the fact that you've been able to push indicates that it's not. http://hg.mozilla.org/hgcustom/hghooks/file/2b48ff549ea9/mozhghooks/single_head_per_branch.py is the actual hook code, for the curious.
Created attachment 532280 [details] commands used in the bash session (from .bash_history) These are the commands used (alas no output) Please note that I also had an update of Compare-Locales interspersed in the flow ;-/ [Custom commands/scripts] ./update-all == "hg pull -u"-script on each repo ./ea == "edit aurora" command that opens both en-US and da file for easy compare ./cl-b-a == envoke Compare Locales for Browser on Aurora script
Noah created those repos in bug 649524.
Bumping to blocker. We need a defined repo state well before the beta move, i.e., now if that move is supposed to be tomorrow.
Severity: critical → blocker
(In reply to comment #6) > We need a defined repo state well before the beta move, i.e., now if that > move is supposed to be tomorrow. I'm enabling the hook on existing l10n/mozilla-aurora repositories now
The hooks seem to be up now, I confirmed that I can't push a new head on x-testing. I also confirmed that the aurora repos now only have a single head on each branch, by running the head-count command from my http://hg.mozilla.org/users/axel_mozilla.com/branch-l10n/ hg extension on all repos. Thanks.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Component: Server Operations: RelEng → RelOps
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.