Better solution IMO is to stagger the builds so they don't contend with each other.

Looking right now the devices are just sitting doing nothing.

This is a problem that we have in general. During peak times we get a lot of chrome changes and a new Chrome version tag so both the incremental builders and the PFQ builders are running full tilt. The rest of the time the machines are idle.

Since the PFQ has a fixed master timeout, if there is resource contention we may get failures when slaves are killed because they did not complete in time.

If we could prioritize PFQ builders over informational builders, that would help a lot.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot