[wdspec] Remove "acceptInsecureCerts" capabilities marker which should no longer be required
Categories
(Remote Protocol :: Marionette, task)
Tracking
(firefox116 fixed)
Tracking | Status | |
---|---|---|
firefox116 | --- | fixed |
People
(Reporter: whimboo, Assigned: whimboo)
References
Details
Attachments
(2 files)
Bug 1839123 - [wdspec] Remove "acceptInsecureCerts" capabilities marker which is no longer required.
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review |
Given that the wdspec tests use the profile under /testing/profiles
now we don't seem to need the acceptInsecureCerts
capabilities marker for pytest anymore.
The following instances exist:
https://searchfox.org/mozilla-central/search?q=%40pytest.mark.capabilities(%7B%22acceptInsecureCerts%22%3A%20True%7D)&path=
When removing those we should still check with Safari and Chrome as well. As such it might be better to make those changes directly in the upstream repository.
This change will most likely fix the intermittent failures as recently seen on bug 1769430.
Assignee | ||
Comment 1•2 years ago
|
||
A try build is at: https://treeherder.mozilla.org/jobs?repo=try&revision=c08233632fe9bf17805f50898afa2fcb67b0887d
The upstream PR for the checks is at: https://github.com/web-platform-tests/wpt/pull/40623
Assignee | ||
Comment 2•2 years ago
|
||
Updated•2 years ago
|
Assignee | ||
Comment 5•2 years ago
|
||
Comment 7•2 years ago
|
||
bugherder |
Comment 8•2 years ago
|
||
bugherder |
Assignee | ||
Comment 10•2 years ago
|
||
(In reply to Pulsebot from comment #6)
Pushed by hskupin@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/2ad5c2418b37
[wdspec] Add back accidentally removed capability selection.
r=webdriver-reviewers,Sasha
Hi James, as it looks like the wpt bot cannot handle two separately landed commits on the same bug, and didn't create the upstream PR.
Updated•2 years ago
|
Assignee | ||
Comment 11•2 years ago
|
||
(In reply to Henrik Skupin [:whimboo][⌚️UTC+2] from comment #10)
Hi James, as it looks like the wpt bot cannot handle two separately landed commits on the same bug, and didn't create the upstream PR.
Actually wpt bot silently folded in this extra commit in the already created PR, which is merged now.
Description
•