Closed Bug 1355260 Opened 7 years ago Closed 7 years ago

'mach try' with a test path does not start mochitest-bc or mochitest-dt e10s tests

Categories

(Testing :: General, enhancement)

enhancement
Not set
normal

Tracking

(firefox54 fixed, firefox55 fixed)

RESOLVED FIXED
mozilla55
Tracking Status
firefox54 --- fixed
firefox55 --- fixed

People

(Reporter: gbrown, Assigned: gbrown)

Details

Attachments

(1 file)

In https://treeherder.mozilla.org/#/jobs?repo=try&revision=8cb4db8ca18fe17d804519935a6686605abff1d7, no e10s jobs were started (I had to "Add new jobs". 

I think mochitest-e10s-browser-chrome-1 needs to be mochitest-browser-chrome-e10s-1.
Summary: 'mach try' with a test path never starts e10s tests → 'mach try' with a test path does not start mochitest-bc or mochitest-dt e10s tests
Comment on attachment 8857182 [details] [diff] [review]
allow mochitest-dt-e10s or mochitest-e10s-dt (and -bc)

Review of attachment 8857182 [details] [diff] [review]:
-----------------------------------------------------------------

Did this change when we moved to TaskCluster? Is that why we have both here?

At any rate this shouldn't cause problems, thank you for the patch.
Attachment #8857182 - Flags: review?(cmanchester) → review+
(In reply to Chris Manchester (:chmanchester) from comment #2)
> Did this change when we moved to TaskCluster? Is that why we have both here?

Yes, I think so.
Pushed by gbrown@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/6b5b027964eb
Allow for variability in mochitest-dt and bc e10s names in try syntax; r=chmanchester
https://hg.mozilla.org/mozilla-central/rev/6b5b027964eb
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: