On 30/09/12 03:43 AM, Justin Lebar wrote:
We're all trying to build the best system we can here. We've been publishing
as much raw data as we can, as well as reports like wait time data for ages.
We're not trying to hide this stuff away.
I understand. My point is just that the data we currently have isn't
what we actually want to measure. Wait times for individual parts of
a try push don't tell the whole story. If Linux-64 wait times go
down, what fraction of people get their full try results faster?
(That is, how often is Linux-64 on the critical path for a try push?)
I honestly don't know.
[snip]
I hope we all agree that by this metric, we're currently failing. The
current infrastructure does not meet demand. (Indeed, demand is
actually higher than the jobs we're currently running, because we
would very much like to disable coalescing on m-i, but we can't do
that for lack of capacity.) All I'm saying is that we currently don't
have the right public data to determine, after X amount of time has
passed, whether we've made any progress in this respect.
I just want to highlight that the data _is_ available publicly through
several different mechanisms.
Raw build data going back to October 2009 is available here:
http://builddata.pub.build.mozilla.org/buildjson/
In addition, per-push information is available via self-serve, e.g.
https://secure.pub.build.mozilla.org/buildapi/self-serve/try/rev/ae6f597c4a09
https://secure.pub.build.mozilla.org/buildapi/self-serve/try/rev/ae6f597c4a09?format=json
The "Try High Scores" data is generated by pulling hg pushlog, and then
looking up each push in self-serve. I'm not relying on private data.
You shouldn't feel blocked by RelEng to get the data that you want. I'd
most likely use these same APIs to look at end-to-end time.
Cheers,
Chris
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
