1278416 - https://hg.mozilla.org/automation/orangefactor in a bad state; can't push new commits

Status: RESOLVED WORKSFORME

(Developer Services :: General, task)

Description

[Jonathan Griffin (:jgriffin)]

I pushed a commit to https://hg.mozilla.org/automation/orangefactor, and got a success message:

pushing to ssh://hg.mozilla.org/automation/orangefactor
searching for changes
remote: adding changesets           
remote: adding manifests
remote: adding file changes
remote: added 1 changesets with 1 changes to 1 files
remote: recorded push in pushlog
remote: 
remote: View your change here:
remote:   https://hg.mozilla.org/automation/orangefactor/rev/1bd7ecbfcb70
remote: recorded changegroup in replication log in 0.002s

But, the new commit does not show up on hgweb, and fresh clones of the repo do not see it. However, if attempting to push another commit on top of a fresh clone, I get this error:

pushing to ssh://hg.mozilla.org/automation/orangefactor
searching for changes
remote has heads on branch 'default' that are not known locally: 1bd7ecbfcb70
abort: push creates new remote head b162db0cd0da!
(pull and merge or see "hg help push" for details about pushing new heads)

And yet, 'hg pull' reports 'no changes found'.

Seems like the commit 1bd7ecbfcb70 is in some weird state, which blocks further pushes to the repo.

Comment 1

[Gregory Szorc [:gps]]

Replication is a bit slow right now because I'm creating the non-experimental version of the Firefox unified repository. The commits will show up in a few minutes.