573250 - pushlog is broken on hg.m.o/projects/maple+birch+cedar

Status: RESOLVED FIXED

(Developer Services :: Mercurial: hg.mozilla.org, defect)

Description

[John Ford [:jhford] CET/CEST Berlin Time]

The push log for the maple, birch and cedar are no longer working.  This is resulting in no builds being triggered from these branches.  I am not sure what was the cause, but the last push that is in our buildbot database was from Friday, before the mercurial work.

http://hg.mozilla.org/projects/maple/pushlog
http://hg.mozilla.org/projects/cedar/pushlog
http://hg.mozilla.org/projects/birch/pushlog

The regular hgweb interface works fine for these repositories.

Loading the pushlog url results in a browser used nearly 100% of my cpu and 700+mb of ram on snow leopard and linux, mozilla-central and 3.5.  It would be good to figure out what data was being sent to the browser so a bug can be filed against the browser not to behave like that.

Comment 1

[Aravind Gottipati [:aravind]]

Probably fallout from the Hg upgrade work yesterday. Looking into it.

Comment 2

[Aravind Gottipati [:aravind]]

It looks like the entire history is being served up in the pushlog, I think this is a bug in pushlog.. The same pushlog gives paginated output for mozilla-central (but not for these repos).  Moving this to the hg component for Ted and others to investigate.

Comment 3

[(not currently active) Ted Mielczarek]

If the changesets were pushed there in one giant push, then the pushlog is doing what it thinks is the right thing, trying to show you the contents of that (enormous) push. We can probably fix the pushlog to detect these cases and do something more sane, but in the future, the right thing to do would be to clone m-c as a starting point, not create an empty repo and push everything to it all at once.

Comment 4

[Nick Thomas [:nthomas] (UTC+12)]

I bet we need to copy the pushlog db over (and fix if appropriate) rather than regenerate it on clone. Pretty sure these project branches were slow before the hg update on Friday.

Comment 5

[(not currently active) Ted Mielczarek]

I don't think that's really correct either, since then you'd have incorrect data in the pushlog. You'd be claiming that things were pushed to a project branch at the same time as the trunk.

Comment 6

[Aravind Gottipati [:aravind]]

I am guessing this is no longer a problem, since we have been using these repos just fine for some time now.  Please re-open if this is still an issue.