-
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
[Discover][UnifiedDataTable] Attempt to fix flaky jest test #201754
[Discover][UnifiedDataTable] Attempt to fix flaky jest test #201754
Conversation
0e3d69a
to
be757a4
Compare
/ci |
/ci |
/ci |
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.
🥳
Pinging @elastic/kibana-data-discovery (Team:DataDiscovery) |
Starting backport for target branches: 8.x https://github.com/elastic/kibana/actions/runs/12066908661 |
💛 Build succeeded, but was flaky
Failed CI StepsTest FailuresMetrics [docs]
History
cc @kertal |
💚 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 `8.x`: - [[Discover][UnifiedDataTable] Fix flaky jest test](#201754) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Matthias Wilhelm","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-11-28T10:19:07Z","message":"[Discover][UnifiedDataTable] Fix flaky jest test\n\nPreventing a flaky jest test by adding waitFor functionality","sha":"d3727a5342e54aaa79586921d0e1b12498c1c7be","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Discover","release_note:skip","v9.0.0","Team:DataDiscovery","backport:prev-minor","Feature:UnifiedDataTable"],"title":"[Discover][UnifiedDataTable] Attempt to fix flaky jest test","number":201754,"url":"https://github.com/elastic/kibana/pull/201754","mergeCommit":{"message":"[Discover][UnifiedDataTable] Fix flaky jest test\n\nPreventing a flaky jest test by adding waitFor functionality","sha":"d3727a5342e54aaa79586921d0e1b12498c1c7be"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/201754","number":201754,"mergeCommit":{"message":"[Discover][UnifiedDataTable] Fix flaky jest test\n\nPreventing a flaky jest test by adding waitFor functionality","sha":"d3727a5342e54aaa79586921d0e1b12498c1c7be"}}]}] BACKPORT--> Co-authored-by: Matthias Wilhelm <[email protected]>
Summary
Fixes #187527
The jest test occasionally failed , and we don't have a good way to reproduce or run a flaky test runner, so this attempt is simple trying out an addtional
waitFor
to see if this could help.PS: I think the root cause could be lazy loading of an involved component, if someone has an idea how to debug this, pls let know 🙏
Checklist