-
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
Re-enable and debug flaky tags test #90762
Conversation
Pinging @elastic/kibana-core (Team:Core) |
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.
So basically we'll be waiting for the test to get flaky again but this time wwe have additional tracing. We have a similar case with ui counters api_integration tests (SO does not get incremented correctly even though we use refresh=wait_for
)
60d3e37
to
f035522
Compare
f035522
to
b5a7974
Compare
@elasticmachine merge upstream |
@elasticmachine merge upstream |
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: |
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Summary
Closes #90552
The DELETE tag test sometimes failed with a 400 code where supertest expected a 200 but I've been unable to track down where exactly this happens and without knowing what the response body is, it's hard to fix. So I added this debugging but after > 80 test runs it still hasn't failed so I'll enable the test again and if there's more failures we should have more information to fix it.
Checklist
Delete any items that are not applicable to this PR.
For maintainers