Open
Bug 1268496
Opened 8 years ago
Updated 2 years ago
mach try should not assume a test path is always in the same job
Categories
(Developer Infrastructure :: Try, defect)
Developer Infrastructure
Try
Tracking
(Not tracked)
NEW
People
(Reporter: ato, Unassigned)
Details
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•6 years ago
|
Product: Core → Firefox Build System
Updated•6 years ago
|
Component: Mach Core → Try
Updated•2 years ago
|
Product: Firefox Build System → Developer Infrastructure
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•