Closed
Bug 1895414
Opened 9 months ago
Closed 9 months ago
[wpt-sync] Sync PR 46126 - Do not block waiting for chromedriver to start up
Categories
(Testing :: web-platform-tests, task, P4)
Testing
web-platform-tests
Tracking
(firefox128 fixed)
RESOLVED
FIXED
128 Branch
Tracking | Status | |
---|---|---|
firefox128 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 46126 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/46126
Details from upstream follow.
Weizhong Xia <weizhong@google.com> wrote:
Do not block waiting for chromedriver to start up
This would save approximately 0.5 second on each test runner restarts. And this should not cause a problem as another connection to the webdriver will be made to init the session, which also happens during initialization stage.
https://github.com/web-platform-tests/wpt/blob/master/tools/wptrunner/wptrunner/testrunner.py#L93
Assignee | ||
Comment 1•9 months ago
|
||
Assignee | ||
Comment 2•9 months ago
|
||
The PR was not expected to affect any tests, but the try push wasn't a success. Check the try results for infrastructure issues
Assignee | ||
Comment 3•9 months ago
|
||
Test result changes from PR not available.
Assignee | ||
Comment 4•9 months ago
|
||
Test result changes from PR not available.
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/be255758e5a1
[wpt PR 46126] - Do not block waiting for chromedriver to start up, a=testonly
Status: NEW → RESOLVED
Closed: 9 months ago
status-firefox128:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 128 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•