-
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: Jest Tests.x-pack/plugins/cases/public/components/case_view - CaseViewPage Tabs breadcrumbs should set the cases title #153336
Labels
failed-test
A test failure on a tracked branch, potentially flaky-test
Feature:Cases
Cases feature
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
Comments
kibanamachine
added
the
failed-test
A test failure on a tracked branch, potentially flaky-test
label
Mar 20, 2023
kibanamachine
added
the
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
label
Mar 20, 2023
Pinging @elastic/response-ops (Team:ResponseOps) |
Pinging @elastic/response-ops-cases (Feature:Cases) |
New failure: CI Build - main |
Skipped. main: f4d8b10 |
cnasikas
added a commit
that referenced
this issue
Jun 27, 2023
## Summary This PR fixes flaky tests in `x-pack/plugins/cases/public/components/case_view/case_view_page.test.tsx`. Some of them were converted to an e2e test as they were too slow to be on a unit test. Successful runs: - a4ed839 (50 times) - 82ccceb (45 times) - 43c47e6 (20 times) Fixes: #149775, #149776, #149777, #149778, #149779, #149780, #149781, #149782, #153335, #153336, #149773, #149774, #149772, #149771, #149770, #149769, #151845, #153336, #153335 Flaky test runner: https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2500 ### Checklist Delete any items that are not applicable to this PR. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios ### For maintainers - [x] This was checked for breaking API changes and was [labeled appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this issue
Jun 27, 2023
## Summary This PR fixes flaky tests in `x-pack/plugins/cases/public/components/case_view/case_view_page.test.tsx`. Some of them were converted to an e2e test as they were too slow to be on a unit test. Successful runs: - elastic@a4ed839 (50 times) - elastic@82ccceb (45 times) - elastic@43c47e6 (20 times) Fixes: elastic#149775, elastic#149776, elastic#149777, elastic#149778, elastic#149779, elastic#149780, elastic#149781, elastic#149782, elastic#153335, elastic#153336, elastic#149773, elastic#149774, elastic#149772, elastic#149771, elastic#149770, elastic#149769, elastic#151845, elastic#153336, elastic#153335 Flaky test runner: https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2500 ### Checklist Delete any items that are not applicable to this PR. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios ### For maintainers - [x] This was checked for breaking API changes and was [labeled appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) (cherry picked from commit c0047a1)
Fixed by #160412 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
failed-test
A test failure on a tracked branch, potentially flaky-test
Feature:Cases
Cases feature
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
A test failed on a tracked branch
First failure: CI Build - main
The text was updated successfully, but these errors were encountered: