Closed Bug 1271664 Opened 10 years ago Closed 10 years ago

manifestparser and subsuite allow browser-chrome tests to run tests that have subsuite=X when we don't specify it when running the test

Categories

(Testing :: General, defect)

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

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: jmaher, Unassigned)

References

Details

I have seen this on tryserver a few times. I am pulling out all the clipboard related tests via |subsuite=clipboard|. This works great except for browser-chrome tests (this included devtools as well). In this case I see locally: |mach test <dir> --subsuite=clipboard| <- this only runs clipboard- OK |mach test <dir>| <- this runs all tests, even with subsuite=clipbard- FAIL I suspect there is some funky logic in the duplicated code for manifest parsing, also that browser-chrome has |subsuite=devtools| as a large chunk of related tests.
hmm, I had reproduced this locally, now I seem to not be able to- maybe there is/was something in my environment- either way I have seen this on try and would like to get this resolved.
ok, I had a series of changes and one change reverted a previous patch partially- sorry for the noise.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.