Closed Bug 1340623 Opened 7 years ago Closed 7 years ago

Some expected job priorities are not being found in list of runnable jobs

Categories

(Tree Management Graveyard :: Treeherder: SETA, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1338102

People

(Reporter: rwood, Assigned: rwood)

Details

This is because in the Job Priority API, when processing and looking for the jobs in the list of runnable jobs returned (job_priorities.py:_process), the testtype in the job priority is switched:

jp.testtype = jp.testtype.replace('e10s-browser-chrome', 'browser-chrome-e10s')

https://github.com/mozilla/treeherder/blob/master/treeherder/seta/job_priorities.py#L28

Then after that, the 'key' is made:

key = jp.unique_identifier()

SO in the ref_data_names_map that was retrieved first, the entry looks like this:

(u'mochitest-e10s-browser-chrome-5', u'asan', u'linux64'): u'test-linux64-asan/opt-mochitest-browser-chrome-e10s-5',

However, in the first part of ref_data_names_map we are searching for:

"mochitest-browser-chrome-e10s-5"

Resulting in the log warning message:

WARNING [treeherder.seta.job_priorities:37] We did not find job priority (taskcluster,mochitest-browser-chrome-e10s-5,asan,linux64) in the list of accepted jobs

This is happening for all of these types of jobs: 'e10s-browser-chrome', 'e10s-devtools-chrome', and 'gl-'.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Product: Tree Management → Tree Management Graveyard
You need to log in before you can comment on or make changes to this bug.