mach try should not assume a test path is always in the same job

NEW
Unassigned

Status

3 years ago
7 months ago

People

(Reporter: ato, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

3 years ago
When using `./mach try … PATH` producing a try syntax of something like "try: … --try-test-paths web-platform-tests:PATH", it should not assume that this test is always batched in the same job across platforms.

Example mach command:

    ./mach try -b do -p win64,linux64,macosx64 testing/web-platform/tests/navigation-timing

Resulting try syntax:

    try: -b do -p win64,linux64,macosx64 -u web-platform-tests-1 -t none --try-test-paths web-platform-tests:testing/web-platform/tests/navigation-timing

This causes the W(1) job to get triggered, which works fine on opt builds, but not on debug because the test is located in W(5) on Linux debug and W(6) on OS X and Windows debug.

Example try run:

    https://treeherder.mozilla.org/#/jobs?repo=try&revision=44699d1978bd35db7fc06b964212531c79a3dd2f

Updated

a year ago
Product: Core → Firefox Build System

Updated

7 months ago
Component: Mach Core → Try
You need to log in before you can comment on or make changes to this bug.