1415867 - Tasks that are not tier 1 should run at a lower priority

Status: NEW

(Firefox Build System :: Task Configuration, task)

Description

[Greg Arndt [:garndt]]

Tasks that do not run as tier 1 should run at a lower priority than tier 1 jobs on that branch.

Perhaps this means running at the lowest priority (which is one step lower than what try runs at) or run one level lower than the default priority for that given branch.

Comment 1

[Geoff Brown [:gbrown]]

(In reply to Greg Arndt [:garndt] from comment #0)
> Tasks that do not run as tier 1 should run at a lower priority than tier 1
> jobs on that branch.

Why? Tiers are currently well defined by the job visibility policy, which deals with visibility and whether the job is sheriffed. I don't think those attributes should be confounded with priority.

This is a generic concern, but consider test-verify as a specific example: It runs at tier 2 because sometimes failure should not cause a backout, but it is engineered to provide quick results and a failed result indicates that the push should be looked at more closely (we want it to run at a high priority so that it can provide an early indication of push quality).