On 2015-11-04 10:55 AM, William Lachance wrote:
1. Relatively deterministic.
2. Something people actually care about and are willing to act on, on a
per-commit basis. If you're only going to look at it once a quarter or
so, it doesn't need to be in Perfherder.
Anyway, just thought I'd open the floor to brainstorming. I'd prefer to
add stuff incrementally, to make sure Perfherder can handle the load,
but I'd love to hear all your ideas.
Someone mentioned "test times" to me in private email.
I do think test times are worth tracking, but probably not in
Perfherder: test times might not be deterministic depending on where /
how they're running (which makes it difficult to automatically detect
regressions and sheriff them on a per commit basis) and regardless
there's too much data to really be manageable by Perfherder's intended
interface even if that problem were magically solved.
As a possible alternative, I believe Kyle Lahnakoski's ActiveData
project (https://wiki.mozilla.org/Auto-tools/Projects/ActiveData)
already *does* track this type of data but last I heard he was looking
for more feedback on how to alert/present it to the platform community.
If you have any ideas on this, please let him know (he's CC'ed). :)
Will
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
