New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reland "[ChromeDriver] Stop using --ignore-certificate-errors" #19377
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Already reviewed downstream.
This is a reland of 8f486945b4c91f67b76e02bfd8c39b0a9cf08089 Original change's description: > [ChromeDriver] Stop using --ignore-certificate-errors > > ChromeDriver was passing --ignore-certificate-errors switch to Chrome, > regardless of whether user wants to ignore certificate errors or not. > Fixing by stop passing this flag to Chrome, and relying on using > Security.setIgnoreCertificateErrors command when user wants to ignore > certificate errors. > > Bug: chromedriver:3148 > Change-Id: I5e8493f4cca48ebaeb211c95cd7fd645891c8659 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1824005 > Reviewed-by: Andrey Kosyakov <caseq@chromium.org> > Commit-Queue: John Chen <johnchen@chromium.org> > Cr-Commit-Position: refs/heads/master@{#699890} Bug: chromedriver:3148 Change-Id: I96ce5e6746af65e01407e7c6c92fed7428d686ec Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1829802 Reviewed-by: Eric Seckler <eseckler@chromium.org> Reviewed-by: Robert Ma <robertma@chromium.org> Commit-Queue: John Chen <johnchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#701614}
f933028
to
4ad60c9
Compare
wpt-firefox-nightly-stability is failing on Taskcluster because of a flaky test:
However, I don't know how the pytest metadata is used and if this could plausibly be related. @AutomatedTester @andreastt @whimboo can any of you take a look at the changes made here and say if there's cause for concern for Firefox? |
@JohnChen0 FYI that this has gotten stuck in export. We're working on tooling to communicate that back to Gerrit earlier, but for now we deal with it manually. |
We do not support permissions yet in Firefox. On our side we expect them all to fail. See our own metadata for that particular file: https://searchfox.org/mozilla-central/source/testing/web-platform/meta/webdriver/tests/permissions/set.py.ini |
Thanks @whimboo, I see in https://wpt.fyi/results/webdriver/tests/permissions/set.py?run_id=343820001&run_id=322430003&run_id=322470001&run_id=311240008 these tests are already failing in Firefox on wpt.fyi as well. I haven't read the tests, but if they make the test sometimes timeout in Firefox I guess you'd need to update your metadata, is that fine? @jgraham how to deal with incoming flakiness nowadays? I checked for other uses of |
But why is it flaky? |
I really don't know why it's flaky, or how seriously to investigate a flaky failure mode. @jgraham if we had guidelines for the Ecosystem Infra rotation for how to handle flakiness in Firefox, what do you think it should say about a case like this one? |
Anyway, I'm confident that this change does not cause the flakiness, so I'm force-merging it. |
This is a reland of 8f486945b4c91f67b76e02bfd8c39b0a9cf08089
Original change's description:
Bug: chromedriver:3148
Change-Id: I96ce5e6746af65e01407e7c6c92fed7428d686ec
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1829802
Reviewed-by: Eric Seckler <eseckler@chromium.org>
Reviewed-by: Robert Ma <robertma@chromium.org>
Commit-Queue: John Chen <johnchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#701614}