-
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
Fix unknown product test flaky behavior #148616
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.
LGTM, but how many times do we run it before we no longer consider it flaky 😅 ?
I managed to reproduce the test failure locally, commenting out the following line:
This line used to be a A few days after it was merged, the first CI failure was observed. I also confirmed locally that the introduced delay fixes the issue, when the So all in all, I'm pretty confident this will fix the flaky behavior. |
Now, that being said, perhaps it would be interesting to make the test more robust, having some sort of |
@elasticmachine merge upstream |
💚 Build Succeeded
Metrics [docs]
History
To update your PR or re-run it, just comment with: |
Fixes elastic#129754 The failing integration test is querying the `/api/status` endpoint before Kibana and ES are completely initialized, and thus, it is getting a _unavailable: Waiting for Elasticsearch_ instead of the expected _critical_. The proposed fix consists in awaiting a few milliseconds, in order to give the `debounceTime` operators enough time to propagate the right status. Co-authored-by: kibanamachine <[email protected]>
Fixes elastic#129754 The failing integration test is querying the `/api/status` endpoint before Kibana and ES are completely initialized, and thus, it is getting a _unavailable: Waiting for Elasticsearch_ instead of the expected _critical_. The proposed fix consists in awaiting a few milliseconds, in order to give the `debounceTime` operators enough time to propagate the right status. Co-authored-by: kibanamachine <[email protected]> (cherry picked from commit 9f39b78)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
# Backport This will backport the following commits from `main` to `7.17`: - [Fix unknown product test flaky behavior (#148616)](#148616) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Gerard Soldevila","email":"[email protected]"},"sourceCommit":{"committedDate":"2023-01-11T14:20:37Z","message":"Fix unknown product test flaky behavior (#148616)\n\nFixes https://github.com/elastic/kibana/issues/129754\r\n\r\nThe failing integration test is querying the `/api/status` endpoint\r\nbefore Kibana and ES are completely initialized, and thus, it is getting\r\na _unavailable: Waiting for Elasticsearch_ instead of the expected\r\n_critical_.\r\n\r\nThe proposed fix consists in awaiting a few milliseconds, in order to\r\ngive the `debounceTime` operators enough time to propagate the right\r\nstatus.\r\n\r\nCo-authored-by: kibanamachine <[email protected]>","sha":"9f39b785620fbc42e30aea774e875bb3048eb2ae","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","test-failure-flaky","backport:skip","v8.7.0"],"number":148616,"url":"https://github.com/elastic/kibana/pull/148616","mergeCommit":{"message":"Fix unknown product test flaky behavior (#148616)\n\nFixes https://github.com/elastic/kibana/issues/129754\r\n\r\nThe failing integration test is querying the `/api/status` endpoint\r\nbefore Kibana and ES are completely initialized, and thus, it is getting\r\na _unavailable: Waiting for Elasticsearch_ instead of the expected\r\n_critical_.\r\n\r\nThe proposed fix consists in awaiting a few milliseconds, in order to\r\ngive the `debounceTime` operators enough time to propagate the right\r\nstatus.\r\n\r\nCo-authored-by: kibanamachine <[email protected]>","sha":"9f39b785620fbc42e30aea774e875bb3048eb2ae"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/148616","number":148616,"mergeCommit":{"message":"Fix unknown product test flaky behavior (#148616)\n\nFixes https://github.com/elastic/kibana/issues/129754\r\n\r\nThe failing integration test is querying the `/api/status` endpoint\r\nbefore Kibana and ES are completely initialized, and thus, it is getting\r\na _unavailable: Waiting for Elasticsearch_ instead of the expected\r\n_critical_.\r\n\r\nThe proposed fix consists in awaiting a few milliseconds, in order to\r\ngive the `debounceTime` operators enough time to propagate the right\r\nstatus.\r\n\r\nCo-authored-by: kibanamachine <[email protected]>","sha":"9f39b785620fbc42e30aea774e875bb3048eb2ae"}}]}] BACKPORT-->
Fixes #129754
The failing integration test is querying the
/api/status
endpoint before Kibana and ES are completely initialized, and thus, it is getting a unavailable: Waiting for Elasticsearch instead of the expected critical.The proposed fix consists in awaiting a few milliseconds, in order to give the
debounceTime
operators enough time to propagate the right status.