Closed Bug 1398510 Opened 8 years ago Closed 8 years ago

[tryselect] Running |mach try fuzzy -q 'linux32 mochitest'| schedules linux64-jsdcov.

Categories

(Testing :: General, enhancement)

Product:
Testing
Component:
General
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: sparky, Unassigned)

Details

Today, I had made a push to try using the following: |mach try fuzzy -q 'linux32 mochitest'| Here is the resulting target task set: https://hg.mozilla.org/try/rev/cd061426840a99e9e88bdb6d47ff4c98af13d6ff It looks like linux64-jsdcov was scheduled because it has a 32nd mochitest-bc. Is this an expected behaviour or a bug?
Flags: needinfo?(ahalberstadt)
It's an expected behaviour, sort of unfortunate but I don't think we should be special casing stuff like this. You can avoid this in the future by putting a single quote in front of a term. That forces the term to be an exact match. So you'd want: ./mach try fuzzy -q "'linux32 mochitest"
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(ahalberstadt)
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.