-
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 Integration Tests.src/core/server/saved_objects/migrationsv2/actions/integration_tests - migration actions reindex & waitForReindexTask resolves left wait_for_task_completion_timeout when the task does not finish within the timeout #103231
Comments
Pinging @elastic/kibana-core (Team:Core) |
Closing as there seems to have been only a single failure |
New failure: CI Build |
New failure: CI Build |
New failure: CI Build |
New failure: CI Build |
New failure: CI Build |
New failure: CI Build |
New failure: CI Build |
New failure: CI Build |
New failure: CI Build |
New failure: CI Build |
New failure: CI Build |
New failure: CI Build |
New failure: CI Build |
To fix the initial failures I used a data archive with a lot more data which avoided the race condition where the reindex operation completes in |
New failure: CI Build |
New failure: CI Build |
New failure: CI Build - 7.16 |
This test seems to be passing on today's hourly builds for 7.16 and 8.0. Based on the history of the flakiness here, should we set time aside to re-evaluate our testing strategy for integration tests? |
The last failure doesn't seem to be flakiness but someone trying to build 7.16 with an 7.17 ES version before we added the necessary support. This created the following errors:
Closing, since the last fix all failures turned out to be noise. |
A test failed on a tracked branch
First failure: Jenkins Build
The text was updated successfully, but these errors were encountered: