1006703 - Requesting twig repo Elm be reset

Status: RESOLVED FIXED

(Developer Services :: General, task)

Description

[Mark Banner (:standard8)]

Please run the script below and reset Elm to m-c. Also please ensure at least the following hooks are added to the repository (or included with):

commit-message
prevent_broken_csets
prevent_case_only_renames
push_printurls

==== Script below ====

export REPO_PATH=mozilla-central
export TWIG=elm

cd /repo/hg/scripts/
./reset_pp_repo.sh -s /repo/hg/mozilla/$REPO_PATH -r tip -d $TWIG

Comment 1

[Kendall Libby [:fubar] (he/him)]

All set. http://hg.mozilla.org/projects/elm/

[hooks]
pretxnchangegroup.a_treeclosure = python:mozhghooks.treeclosure.hook
pretxnchangegroup.b_preventcsetbreakage = python:mozhghooks.prevent_broken_csets.hook
pretxnchangegroup.c_preventcaseonly = python:mozhghooks.prevent_case_only_renam.hook
pretxnchangegroup.d_commitmessage = python:mozhghooks.commit-message.hook
changegroup.push_printurls = python:mozhghooks.push_printurls.hook

Comment 2

[Mark Banner (:standard8)]

I've just tried pushing to elm and I get:

remote: abort: pretxnchangegroup.c_preventcaseonly hook is invalid (import of "mozhghooks.prevent_case_only_renam" failed)

Should that have been "mozhghooks.prevent_case_only_renames"?

Comment 3

[Kendall Libby [:fubar] (he/him)]

Yep, typo. Fixed. Also, asked #releng to prod the buildbot scheduler, which I should have done yesterday.

Comment 4

[Mark Banner (:standard8)]

Just tried this again:

pushing to ssh://hg.mozilla.org/projects/elm
searching for changes
remote: waiting for lock on repository /repo/hg/mozilla/projects/elm held by 'hgssh1.dmz.scl3.mozilla.com:25577'
remote: abort: repository /repo/hg/mozilla/projects/elm: timed out waiting for lock held by hgssh1.dmz.scl3.mozilla.com:25577
abort: unexpected response: empty string

Not sure what's happening there.

Comment 5

[Kendall Libby [:fubar] (he/him)]

Ok, that's really interesting. Normally, we only see that with folks pushing to try, and someone else has a long running push. I wish I knew what process 25577 was. :-\
Did you have any other pushes prior to that one?

Comment 6

[Mark Banner (:standard8)]

(In reply to Kendall Libby [:fubar] from comment #5)
> Ok, that's really interesting. Normally, we only see that with folks pushing
> to try, and someone else has a long running push. I wish I knew what process
> 25577 was. :-\
> Did you have any other pushes prior to that one?

Yes I did, I had assumed it had hung and so killed it, but maybe it hadn't.

Comment 7

[Kendall Libby [:fubar] (he/him)]

Ah, ok. The remote hg process takes a little while to die - either from cleaning up, or waiting for it to finish whatever it had been doing (likely computing ancestry) first. 

Try the push again, but let it run or time out. If it takes a really long time, please let me know. Thanks!

Comment 8

[Mark Banner (:standard8)]

We changed hooks around last week, and I've just been able to push to this repo again, and it was fine :-)