I'm fine with overriding the existing suite priorities. But ideally, making test_priorities a sub-priority under suite's priorities is making more sense to me. So we do not get extra provision based on test_priorities overlapped with suite_priorities. But, in this case, we may have to deal with the scheduler.

In moblab we do not have suite priorities ( just the default priority is used ) so for now it makes the most sense to do it this way.

I agree if we want to make this more general it would require some work and increase based on a value of the suite priority.  At the moment I am just trying to optimize moblab as much as possible.

I think the idea by pwang in #1 is better than mine using deltas, as the latter will trigger reordering of suites/reprovisioning which is undesirable. I am ok if moblab experiments with new features, but ultimately it is best for everyone if there is not too much divergence.

Just curious, why moblab does not have suite priority? What is the priority while user trying to schedule a suite? Can user specify their own priority to the suite? If so, would they expect the priority being overridden by test_priorities?

There is no suite scheduler on moblab and they are not running build / cq so there is really no need.  It is not that it is not there, there is just no need for it so it is not exposed in the UI.

Partners typically want to run a single suite at a time, until completion, there is never any overlap hence priorities are not required.