Since we are limited on the number of these we can do per week (to 2)
we would like these to happen fairly promptly after the time given in
the crontab, otherwise we can potentially end up with the Wednesday
run not actually happening until late Saturday, right before the
Sunday run which might happen right away.
Therefore specify OSSTEST_RESOURCE_PRIORITY=-15, which is right behind
xen-unstable-smoke in priority order.
We don't have much data yet but based on what we have so far
ts-coverity-build takes up to 1000s (around quarter of an hour) and
ts-coverity-upload a little over half an hour. So including host
install (if needed, it can use a share of an existing build host if
one is around) the whole thing comes in at well under an hour, so
having this slip to the head of the queue is unlikely to cause
problems.
Also put mg-allocate and mg-blockage in the correct order in the doc.
Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
in the more distant future.
Values for OSSTEST_RESOURCE_PRIORITY:
- mg-allocate -1000000
mg-blockage -2000000
+ mg-allocate -1000000
cr-try-bisect-adhoc -30
xen-unstable-smoke cr-daily-branch -20
+ xen-unstable-coverity cr-daily-branch -15
default Executive.pm with controlling terminal -10
mg-execute-flight -8
default 0
--- /dev/null
+export OSSTEST_RESOURCE_PRIORITY=-15