564349 - Investigate using pushloghtml?tipsonly=1 for try server

Status: RESOLVED WONTFIX

(Tree Management Graveyard :: TBPL, defect)

Description

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

The tipsonly option dramatically reduces the time to retrieve the list of changes, but does it remove useful data too ?

Comment 1

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

$ time curl -s "http://hg.mozilla.org/try/pushlog?tipsonly=1" > /dev/null
real	0m1.363s
user	0m0.005s
sys	0m0.009s

$ time curl -s "http://hg.mozilla.org/try/pushlog" > /dev/null
real	0m9.296s
user	0m0.029s
sys	0m0.090s

for a refreshing reset try repo plus 1.9.2 pushed (added 2736 changesets with 8284 changes to 9647 files (+18 heads)).

Comment 2

[Phil Ringnalda (:philor)]

Afraid it does remove useful data: I typically push 10 things out of checkin-needed, with little or no idea which 10, then when that fails push them in 5 sets of 2, and see which one fails. With tipsonly, only having one of the set listed, I'd then have to go back and forth between tbpl and a non-tipsonly pushloghtml to figure out what was actually in each push. Even for someone's own patches, it's not unusual to hear "why did that fail on try? oh, I didn't push the other thing it needs...".

Comment 3

[Markus Stange [:mstange]]

What we could do is use pushloghtml?tipsonly=1 to get the basic pushlog loaded quickly and then load pushloghtml?changeset=rev for every push and reassemble everything, right? That would be some work but it would make trytbpl much more usable without removing useful data.

Comment 4

[Arpad Borsos [:Swatinem]]

We don’t use pushloghtml any more since bug 584836. That made pushlog also a lot faster and more useable, making this a WONTFIX then.