The queueing order is determined by the job priority value. Each
client declares its own priority. The usual basis for the priority is
-is client's starting time_t. So by and large jobs execute in order.
+is client's starting time_t. So by and large jobs execute in
+order. This can be overridden using $OSSTEST_RESOURCE_WAITSTART.
The main client in the planning process is
ts-hosts-allocate-Executive. That program contains the heuristics for
Values for OSSTEST_RESOURCE_PRIORITY:
mg-allocate -1000000
mg-blockage -2000000
+ cr-try-bisect-adhoc -30
xen-unstable-smoke cr-daily-branch -20
default Executive.pm with controlling terminal -10
mg-execute-flight -8
default 0
+Values for OSSTEST_RESOURCE_WAITSTART:
+ cr-try-bisect 6000 seconds before the timestamp on the
+ corresponding $branch.mro file (i.e. 6000
+ before the end of the real flight which
+ triggered the bisection attempt).
ms-ownerdaemon and `ownd' tasks
-------------------------------