Closed
Bug 672231
Opened 13 years ago
Closed 13 years ago
Pushing to try is slow
Categories
(Release Engineering :: General, defect, P3)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jrmuizel, Unassigned)
References
Details
(Whiteboard: [tryserver][cleanup][hg][buildduty])
:(
Reporter | ||
Comment 1•13 years ago
|
||
It says:
searching for changes
for a long time.
Updated•13 years ago
|
Assignee: nobody → server-ops-releng
Component: Release Engineering → Server Operations: RelEng
QA Contact: release → zandr
Updated•13 years ago
|
Assignee: server-ops-releng → nobody
Component: Server Operations: RelEng → Release Engineering
QA Contact: zandr → release
Comment 2•13 years ago
|
||
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•13 years ago
|
||
(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.
Whiteboard: [needinfo]
Reporter | ||
Comment 4•13 years ago
|
||
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
Updated•13 years ago
|
Whiteboard: [needinfo]
Comment 5•13 years ago
|
||
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•13 years ago
|
||
are we not automatically pruning regularly?
Comment 7•13 years ago
|
||
I think we keep deferring actually testing that. Eg bug 554656, bug 652680.
Comment 8•13 years ago
|
||
Even better - bug 633161.
Comment 9•13 years ago
|
||
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
Reporter | ||
Comment 10•13 years ago
|
||
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•13 years ago
|
||
Work is progressing in bug 676420.
Severity: normal → major
OS: Mac OS X → All
Priority: -- → P3
Hardware: x86 → All
Whiteboard: [tryserver][cleanup][hg][buildduty]
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•