Open Bug 1783234 Opened 3 years ago Updated 3 years ago

test-verify tasks selected in `mach try fuzzy` aren't triggered

Categories

(Developer Infrastructure :: Try, defect, P3)

Product:
Developer Infrastructure
Component:
Try
Type:
defect

Tracking

(Not tracked)

People

(Reporter: nchevobbe, Unassigned)

Details

I think it occured to me twice now, that a push that is the result of ./mach try fuzzy path/to/test/file doesn't trigger the jobs I selected (TV in that case), e.g. : https://treeherder.mozilla.org/jobs?repo=try&revision=ed0f3bf471bb6362e9788beea9e09a4d71d20507

I believe this is happening because the number of chunks resolved locally is different than the number of chunks that are resolved when the decision task runs on try. So locally the label has a -1 appended to the chunk but in CI it doesn't. Since the requested label doesn't match the one that exists, it never gets selected to run.

Summary: Job selected in fuzzy aren't triggered → test-verify tasks selected in `mach try fuzzy` aren't triggered
Product: Firefox Build System → Developer Infrastructure

The severity field is not set for this bug.
:ahal, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(ahal)
Severity: -- → S3
Flags: needinfo?(ahal)
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.