-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Flaky io.trino.tests.jdbc.TestExternalAuthorizerOAuth2 #6991
Comments
One idea is to replace Selenium with plain HTTP client. Where we it will be easier to control and debug. However:
Possibly we could reuse some IdP REST API, but REST API is very specific to IdP. So it is not portable at all. |
I understand this flaky test is being added in #6917. I do hope we will have some sufficient mitigation (e.g. retries) in place before it gets merged. We have enough flaky tests problems already. |
It is is using Selenium, so there is a risk it is flaky. We don't know that yet if it is flaky or not for sure. |
Repeats there are tricky, as we can never be sure 100%, what state will we be left in, with only part of the flow successful. The best option seems to be start over from scratch. |
As I understand you mean to restart the test (by using |
see #8739 (comment) |
https://github.com/trinodb/trino/runs/4350956840?check_suite_focus=true
cc @s2lomon |
CC: @Praveen2112 as you recently added more environemnts. Maybe we should use playwright here. |
Instead of using selenium driver to log in and accept the consent request use a simple python implementation which accepts all requests thus eliminating the need of web driver entirely. Fixes trinodb#6991
Instead of using selenium driver to log in and accept the consent request use a simple python implementation which accepts all requests thus eliminating the need of web driver entirely. Fixes trinodb#6991
Instead of using selenium driver to log in and accept the consent request use a simple python implementation which accepts all requests thus eliminating the need of web driver entirely. Fixes trinodb#6991
Main reason of supposed flakiness is the Selenium WebDriver. This test has a lot of value, but there is a possibility that it will be flaky (it has failed at least once during review process). The plan is to monitor its flakiness and replace it at one point with something less flaky than selenium web driver, if its flakiness will be proved. Similar flaky test: #6223
The text was updated successfully, but these errors were encountered: