Open Bug 1917819 Opened 5 months ago Updated 1 month ago

Specifying xpcshell test file path for mach try fuzzy runs no tasks

Categories

(Developer Infrastructure :: Try, defect)

defect

Tracking

(firefox-esr128 unaffected, firefox132 wontfix, firefox133 wontfix, firefox134 wontfix, firefox135 wontfix)

ASSIGNED
Tracking Status
firefox-esr128 --- unaffected
firefox132 --- wontfix
firefox133 --- wontfix
firefox134 --- wontfix
firefox135 --- wontfix

People

(Reporter: jjalkanen, Assigned: aryx)

References

(Regression)

Details

(Keywords: regression)

Attachments

(1 file)

Previously, issuing ./mach try fuzzy dom/indexedDB/test/unit/test_index_getAll.js --full -q 'testlinux64qrdebugxpcshell' chose the tasks matching the characters in the query 'testlinux64qrdebugxpcshell' and executed the test case with a path dom/indexedDB/test/unit/test_index_getAll.js , as expected.

Currently, issuing the same request runs the linters, a decision task and does nothing else, see https://treeherder.mozilla.org/jobs?revision=9a3b56724490041e57e28875831c8d2431766c50&repo=try.

Specifying a directory path (or leaving the path out), as in ./mach try fuzzy dom/indexedDB/test/unit/ --full -q 'testlinux64qrdebugxpcshell' works as expected and runs all the tests in the specified directory.

Could we please get back the functionality to run only specified tests?

Andrew, do you know what changed this behavior?

Severity: -- → S3
Flags: needinfo?(ahal)

No, I'm not aware of anything that I'd expect to cause this. Though to be honest I'm kind of surprised that running specific tests used to work. I always thought that was unsupported and recommended folks pass in directories instead.

Here is the function responsible for filtering tasks by path:
https://searchfox.org/mozilla-central/rev/43450868e9f3e26da88a02837e5a43c93728ea95/tools/tryselect/tasks.py#166

It does look like there was a substantial refactor to it back in June, so maybe that was the regression? This was bug 1898051

Flags: needinfo?(ahal)
Assignee: nobody → aryx.bugmail
Status: NEW → ASSIGNED

Set release status flags based on info from the regressing bug 1898051

Set release status flags based on info from the regressing bug 1898051

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: