Open Bug 1547040 Opened 6 months ago Updated 3 months ago

--try-test-paths isn't respected anymore

Categories

(Firefox Build System :: Task Configuration, defect)

defect
Not set

Tracking

(Not tracked)

People

(Reporter: florian, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: regression)

See https://treeherder.mozilla.org/#/jobs?repo=try&revision=a3c96ad4ebe9c9cd14c00f2d09ddaab8832ee227 where the tests that ran are from random folders that don't match what's on the try syntax.

This caused me to get backed out because I thought I had a green try push when many of the relevant tests failed :(

https://treeherder.mozilla.org/#/jobs?repo=try&author=mozilla%40noorenberghe.ca&group_state=expanded&fromchange=986835c6a0663b2b10ec8a26358c001bdf631da6&tochange=d8daab1e13fa0ad3c201a94bbfb77b5bb5de8f31

Tom, can you triage please?

Blocks: mach-busted
Flags: needinfo?(mozilla)
Flags: needinfo?(mozilla) → needinfo?(catlee)

I'm not sure I have anything to offer here.

Is this still a problem?

Flags: needinfo?(catlee)

It seems to wfm, but then I run into bug 1541424 instead. Florian, is that what you're seeing too?

Flags: needinfo?(florian)

(In reply to :Gijs (he/him) from comment #4)

It seems to wfm, but then I run into bug 1541424 instead. Florian, is that what you're seeing too?

No. I just pushed to try again to verify: https://treeherder.mozilla.org/#/jobs?repo=try&revision=f05a9cfcd5ad5d8ebf006e7d6ce8de0cf9029fb4

The try syntax contains --try-test-paths browser-chrome:browser/base/content/test/performance but tests in other folders are being run.

Flags: needinfo?(florian)

Just to note, --try-test-paths is a try syntax only mechanism that predates mach try fuzzy and the path scheduling used in bug 1541424. I would like to migrate try syntax to the new mechanism (bug 1400295) and remove --try-test-paths support from the try parser/mozharness.

We can leave this open for now, but if bug 1400295 lands before this one, this will be WONTFIXed.

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