...as its getting slow again. :bz reports 3m52s to push. (bug#734225 has details of work to do this merging automatically, but kicking this off manually today, just to make TryServer life better today)

from irc, last time heads-merged in try repo was 07may2012.

ftr - a clone not updated since 2012-06-04 15:00 PT had 22 heads. current try clone has 2727 heads. That's a lot for 24 hours

(In reply to Hal Wine [:hwine] from comment #2) > ftr - a clone not updated since 2012-06-04 15:00 PT had 22 heads. IGNORE comment #2 - because of where I got my first clone (a try builder) the first value (22 heads) may be seriously under counted.

Update: this process is taking longer than first estimated. Started with 2727 heads at 1500PT (approx), now at 1950 heads at 2130PT. Script prunes to 200 heads, so still a ways to go.

Done - completed at 05:37PT. Repo passes hg verify, pushed. [hwine@github-sync1-dev.dmz.scl3 try]$ timeit hg --cwd $PWD verify checking changesets checking manifests crosschecking files in changesets and manifests checking files 113038 files, 122450 changesets, 613275 total revisions [hwine@github-sync1-dev.dmz.scl3 try]$ [hwine@github-sync1-dev.dmz.scl3 try]$ timeit hg --cwd $PWD push pushing to ssh://try/try searching for changes note: unsynced remote changes! remote: adding changesets remote: adding manifests remote: adding file changes remote: added 2208 changesets with 17367 changes to 5377 files (-2208 heads) remote: Looks like you used try syntax, going ahead with the push. remote: If you don't get what you expected, check http://trychooser.pub.build.mozilla.org/ 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.

Hmm. So I just tried timing a try push today (for the first time since this bug was fixed), and it took 4m45s wall-clock... :( Not sure whether we have lots of heads again or whether something else is up.

Thanks for the update - I cited it in bug 734225 comment 17. Since bug 734225 is the long term solution, please add further updates there.