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)
Testing
General
Tracking
(firefox54 fixed, firefox55 fixed)
RESOLVED
FIXED
mozilla55
People
(Reporter: gbrown, Assigned: gbrown)
Details
Attachments
(1 file)
1.07 KB,
patch
|
chmanchester
:
review+
|
Details | Diff | Splinter Review |
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•7 years 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•7 years ago
|
||
This works much better in my experience: https://treeherder.mozilla.org/#/jobs?repo=try&revision=343269688e459e8f459d37e2f30ba1bc05bb3da8
Attachment #8857182 -
Flags: review?(cmanchester)
Comment 2•7 years ago
|
||
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•7 years 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.
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•7 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/6b5b027964eb
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox55:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
Comment 6•7 years ago
|
||
bugherder uplift |
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.
Description
•