It says: searching for changes for a long time.
So .. this was not much to go on! Did things get better? Worse? Did the push ever finish? Are others having the same problem? If this is better now, can we close this up?
(In reply to comment #2) > So .. this was not much to go on! > > Did things get better? Worse? Did the push ever finish? Are others having > the same problem? If this is better now, can we close this up? Still waiting for info.
Yes this is still bad: pushing to ssh://hg.mozilla.org/try/ searching for changes remote: adding changesets remote: adding manifests remote: adding file changes remote: added 1 changesets with 0 changes to 1 files (+1 heads) remote: Looks like you used try syntax, going ahead with the push. remote: If you don't get what you expected, check http://people.mozilla.org/~lsblakk/trychooser/ for help with building your trychooser request. remote: Thanks for helping save resources, you're the best! remote: Trying to insert into pushlog. remote: Please do not interrupt... remote: Inserted into the pushlog db successfully. real 1m28.831s user 0m1.125s sys 0m0.260s
We have > 4000 heads in try right now. https://bugzilla.mozilla.org/show_bug.cgi?id=529156#c1 makes it seem like >1000 is a problem. I think we need to prune the try repo again.
are we not automatically pruning regularly?
Even better - bug 633161.
I've hit this the last two times I've used the try server. In both cases its sits at "searching for changes" for 10-15 mins, before I kill it. What is the right response, let it sit forever, or kill it and redo? I know once when this happened to me I held a lock on a db as a result of killing it. FWIW, I've just killed it again, in case that is going to cause a lock: hospitality:joystick dave$ hg push -f ssh://email@example.com@hg.mozilla.org/try/ pushing to ssh://firstname.lastname@example.org@hg.mozilla.org/try/ searching for changes ^Cinterrupted! remote: adding changesets remote: adding manifests remote: adding file changes remote: added 6 changesets with 36 changes to 38 files (+2 heads) remote: Killed by signal 2
I also get this: remote: abort: repository /repo/hg/mozilla/try/: timed out waiting for lock held by dm-svn02.mozilla.org:8703
Work is progressing in bug 676420.