Closed
Bug 1545147
Opened 6 years ago
Closed 5 years ago
Run browser-chrome tests in new subsuite
Categories
(Remote Protocol :: Agent, enhancement, P3)
Remote Protocol
Agent
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: ato, Assigned: ochameau)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
The browser-chrome tests are running under the M-bc* jobs on try,
but for better visibility we should create a new test job that is
specific to the remote protocol. This would also allow for better
test scheduling.
Name suggestions for the new mochitest test job are gladly accepted.
|
Reporter | |
Comment 1•6 years ago
|
||
This would involve adding the following to remote/test/browser/browser.ini:
subsuite = remote
And adding some resolve patterns to
https://searchfox.org/mozilla-central/source/testing/mozbase/moztest/moztest/resolve.py.
ahal mentioned that the latter is going to change significantly in
the near future.
Type: defect → enhancement
Priority: -- → P3
|
Assignee | |
Updated•6 years ago
|
Assignee: nobody → poirot.alex
|
|
Assignee | |
Comment 2•6 years ago
|
||
Pushed by apoirot@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/9890048a9f4e
Run remote agent's mochitests in a distinct "remote" job. r=ahal
|
||
Comment 4•5 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•