Open
Bug 1316418
Opened 8 years ago
Updated 2 years ago
By default mach try should take the intersection of test paths/tags instead of the union
Categories
(Developer Infrastructure :: Try, defect)
Developer Infrastructure
Try
Tracking
(Not tracked)
NEW
People
(Reporter: keeler, Unassigned)
References
Details
Using trychooser, I came up with the command ./mach try -b do -p linux64,android-api-15 -u xpcshell -t none --tag psm This resulted in https://treeherder.mozilla.org/#/jobs?repo=try&revision=3db3e1212c5cc7b8f5bcded677bdd36c3308d1d4 which thinks the try syntax was try: -b do -p linux64,android-api-15 -u mochitest-1,mochitest-browser-chrome-1,mochitest-e10s-1,mochitest-e10s-browser-chrome-1,mochitest-o,xpcshell -t none --tag psm --try-test-paths browser-chrome:browser/base/content/test/general browser-chrome:security/manager/ssl/tests/mochitest/browser chrome:security/manager/ssl/tests/mochitest/stricttransportsecurity mochitest:security/manager/ssl/tests/mochitest/stricttransportsecurity which is a little surprising.
Comment 1•8 years ago
|
||
I think |mach try| takes the union of specified paths/tags by default. So your try push is saying "Run any test that is either xpcshell OR has the psm tag". To instead use the intersection, you need to pass in --and. I think what you want is: ./mach try -b do -p linux64,android-api-15 -u xpcshell -t none --and --tag psm Fwiw, I think this is counter intuitive and the intersection should be the default behaviour.
Summary: mach try scheduled tests I didn't ask for → By default mach try should take the intersection of test paths/tags instead of the union
Updated•5 years ago
|
Component: General → Try
Product: Testing → Firefox Build System
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
•