On 01/27/2014 03:36 PM, Ehsan Akhgari wrote:
On 1/27/2014, 7:44 AM, Andrew Halberstadt wrote:
A downside to chunking such that skipped tests are taken into
account is that it will make some chunks take longer to run than
others. This negatively impacts the scheduling algorithms and
ultimately increases infrastructure load.
I assume you are talking about the tests that are skipped in the
manifest, not on the command line, right? In that case, yes. But I
should also note that using the test file count as a proxy for the
runtime requirements is... poor. :-)
Yeah it's poor, but our tooling has a long way to go before we can start
making decisions on better information than that :)
I think there are better ways to solve this problem. I.e a more
expressive try syntax such that you can just specify the test or
directory of tests to run and not care about what chunk it is in.
Bonus points if we can configure mozharness to run only those tests
and ignore all other tests that happen to be in the same chunk.
But doesn't that mean that the code which decides what jobs to
schedule should know about what will happen as part of those jobs? I
may be wrong, but to the best of my knowledge, that information
doesn't exist where we would want trychooser to use it.
I admit I'm not too familiar with trychooser or even buildbot for that
matter. But I do know that the scheduling step happens before the
mozharness step. And I also know that mozharness has access to the
buildbot json. So I imagine there would be a way to pass this
information along to the harness, though someone from releng could
probably clarify this for sure.
Cheers,
Andrew
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
