-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Failing test: Chrome X-Pack Security Functional Tests (Login Selector).x-pack/test/security_functional/tests/login_selector/basic_functionality·ts - security app - login selector Basic functionality can login after Unauthorized
error during request authentication preserving original URL
#98562
Comments
New failure: Jenkins Build |
New failure: Jenkins Build |
New failure: Jenkins Build |
Pinging @elastic/kibana-security (Team:Security) |
@azasypkin I think this one is related to the improved |
Sure, thanks for the ping! |
I found the root cause, but not sure how to fix that yet. Between the moment when we disable current user (to simulate error in the authentication pipeline) and the moment when we refresh current page Kibana sends a number of API requests that fail with 401 and client side interceptor forces logout right before WebDriver refreshes page. |
New failure: CI Build - 7.16 |
It seems the test fails on 7.16 only (for now). We used flaky test runner only on https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/193 |
No luck, CI and Flaky Test runner are completely happy. Will try to figure this out. |
A test failed on a tracked branch
First failure: Jenkins Build
The text was updated successfully, but these errors were encountered: