Last Comment Bug 672231 - Pushing to try is slow
: Pushing to try is slow
Status: RESOLVED FIXED
[tryserver][cleanup][hg][buildduty]
:
Product: Release Engineering
Classification: Other
Component: Other (show other bugs)
: other
: All All
: P3 major (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
:
Mentors:
Depends on: 676420
Blocks:
  Show dependency treegraph
 
Reported: 2011-07-18 09:14 PDT by Jeff Muizelaar [:jrmuizel]
Modified: 2013-08-12 21:54 PDT (History)
11 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---


Attachments

Description Jeff Muizelaar [:jrmuizel] 2011-07-18 09:14:39 PDT
:(
Comment 1 Jeff Muizelaar [:jrmuizel] 2011-07-18 09:18:34 PDT
It says:
searching for changes
for a long time.
Comment 2 Dustin J. Mitchell [:dustin] 2011-07-25 21:27:42 PDT
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?
Comment 3 Aki Sasaki [:aki] 2011-08-02 09:45:05 PDT
(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.
Comment 4 Jeff Muizelaar [:jrmuizel] 2011-08-02 11:00:42 PDT
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
Comment 5 Aki Sasaki [:aki] 2011-08-02 16:28:58 PDT
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.
Comment 6 Chris AtLee [:catlee] 2011-08-02 16:33:16 PDT
are we not automatically pruning regularly?
Comment 7 Nick Thomas [:nthomas] 2011-08-02 16:37:00 PDT
I think we keep deferring actually testing that. Eg bug 554656, bug 652680.
Comment 8 Nick Thomas [:nthomas] 2011-08-02 16:43:45 PDT
Even better - bug 633161.
Comment 9 David Humphrey (:humph) 2011-08-02 17:14:18 PDT
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://david.humphrey@senecac.on.ca@hg.mozilla.org/try/
pushing to ssh://david.humphrey@senecac.on.ca@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
Comment 10 Jeff Muizelaar [:jrmuizel] 2011-08-04 13:43:38 PDT
I also get this:

remote: abort: repository /repo/hg/mozilla/try/: timed out waiting for lock held by dm-svn02.mozilla.org:8703
Comment 11 Chris Cooper [:coop] 2011-08-04 14:18:22 PDT
Work is progressing in bug 676420.

Note You need to log in before you can comment on or make changes to this bug.