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

RESOLVED FIXED in Firefox 54

Status

Testing
General
RESOLVED FIXED
8 months ago
7 months ago

People

(Reporter: gbrown, Assigned: gbrown)

Tracking

Trunk
mozilla55
Points:
---

Firefox Tracking Flags

(firefox54 fixed, firefox55 fixed)

Details

Attachments

(1 attachment)

(Assignee)

Description

8 months ago
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.
(Assignee)

Updated

8 months ago
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
(Assignee)

Comment 1

8 months ago
Created attachment 8857182 [details] [diff] [review]
allow mochitest-dt-e10s or mochitest-e10s-dt (and -bc)

This works much better in my experience:

https://treeherder.mozilla.org/#/jobs?repo=try&revision=343269688e459e8f459d37e2f30ba1bc05bb3da8
Attachment #8857182 - Flags: review?(cmanchester)
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+
(Assignee)

Comment 3

8 months ago
(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.

Comment 4

8 months ago
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

Comment 5

8 months ago
bugherder
https://hg.mozilla.org/mozilla-central/rev/6b5b027964eb
Status: NEW → RESOLVED
Last Resolved: 8 months ago
status-firefox55: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
https://hg.mozilla.org/releases/mozilla-beta/rev/29e9a1d26de8
status-firefox54: --- → fixed
You need to log in before you can comment on or make changes to this bug.