-
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
[Flaky test]: apis Kerberos security Kerberos authentication finishing SPNEGO should properly set cookie and authenticate user #68836
Comments
Pinging @elastic/kibana-security (Team:Security) |
Pinging @elastic/kibana-test-triage (failed-test) |
Alternatively these PRs weren't rebased on latest master where we updated this test, but were using the latest promoted snapshot, or something along these lines. Not sure if it is possible |
* master: (38 commits) Support migrating from reserved feature privileges (elastic#68504) add `preference` field to SavedObjectsFindOptions (elastic#68620) [ILM] Add "wait for snapshot" policy field to Delete phase (elastic#68505) Cleanup old license overwrites (elastic#68744) Bump TypeScript to v3.9 (elastic#67666) [APM] Service maps - adds new storybook stories to test out various data sets (elastic#68727) Fix vega specification parsing (elastic#67963) docs: add more api information (elastic#68717) [APM] Don't show annotations on charts with no data (elastic#68829) [Metrics UI] Fix Inventory View sorting by handling null values (elastic#67889) skip flaky suite (elastic#68836) [SIEM][Detections Engine] - Fix reference rule url overflow (elastic#68640) Index pattern public api => common (elastic#68289) [APM] Lazy-load alert triggers (elastic#68806) [DOCS] Fix table formatting in ingest manager settings (elastic#68824) [Endpoint] Functional Tests cleanup (elastic#68756) revert previous commit which was unintentional Use Github token instead for project assignments [SIEM][Exceptions] - ExceptionsViewer cleanup (elastic#68739) move @kbn/storybook to devDeps (elastic#68791) ...
@spalger is there any way to figure out what Kibana and ES snapshot revisions these failing PRs used to validate my hypothesises outlined in #68836 (comment) and #68836 (comment)? I tend to think that it was just an unfortunate coincidence that triggered that false alarm and we should unskip these tests. |
I went ahead and re-enabled the tests. If it turns out that my theory was wrong, I'll take a deeper look. |
We have a flaky test that has only shown up on PRs but is very flaky, failing 48 times in the last 24 hours:
stack trace
stdout
The text was updated successfully, but these errors were encountered: