tree 909a5198c818977fc336f90d24e3163038475631
parent aca430c872c68bbbdf10f45b94f7d947001f9d95
author Jonathan Lee <jonathan-j-lee@users.noreply.github.com> 1686787086 -0700
committer GitHub <noreply@github.com> 1686787086 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJkilQOCRBK7hj4Ov3rIwAAVkIIABn3HKzD6i2sR8xCAZCwBFiy
 fKHOsHke+FZEIPylHY0K39Bwyx0Ot2b5rnSgPVhDOSNw4xKXJGOqtvIPVVo38BEj
 4Qx5mNOIA/K5xy0NjR9h100wqx3jlU9f0C20EZ7Qtt/R+6/3sC7nZzBdW4jh9qCv
 NZsU9jRXfrhF2Px4RW4D02PD+g/o88EQI9EQgcF66aaMfZWAm94IlZyQDOnli3FO
 Ug5opzd431op5PiCtimFSGo3tV3bewO1W9VMf08hU3e2rCfkI5Qo6xwBCQmTc/Xd
 n3PgX4D0164hV/BTTaEpI+WFVl10yEYTXw6PFQQwp83GSkectB44FmboFrDP0jc=
 =uV9J
 -----END PGP SIGNATURE-----
 

[wptrunner] Run larger groups first (#39613)

This change orders groups within each test type in the test queue by
decreasing total timeout for multi-process runs. This heuristic attempts
to distribute work to test runners more evenly by scheduling small
groups around larger ones.

A large group that runs near the end of the suite cannot be split, so
some runners may become idle while waiting for stragglers. For example,
[0] shows a run where there's a 1 min gap between the first and last
idle processes in the initial run.

Empirically, in Chromium CI, this change reduces total test runtime
meaningfully:
  Chrome on Linux: ~120 min [1] -> ~115 min [2]
  Content Shell on Linux: ~100 min [3] -> ~90 min [4]

[0]: https://chromium-swarm.appspot.com/task?id=62b302bbdd0bbf10
[1]: https://ci.chromium.org/ui/p/chromium/builders/ci/linux-wpt-fyi-rel/42930/overview
[2]: https://ci.chromium.org/ui/p/chromium/builders/try/linux-wpt-fyi-rel/2035/overview
[3]: https://ci.chromium.org/ui/p/chromium/builders/ci/linux-wpt-content-shell-fyi-rel/9981/overview
[4]: https://ci.chromium.org/ui/p/chromium/builders/try/linux-wpt-content-shell-fyi-rel/1850/overview