-
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/integration_tests/saved_objects/migrations - migration v2 migrates saved objects normally when multiple Kibana instances are started with a small interval #148263
Labels
failed-test
A test failure on a tracked branch, potentially flaky-test
Team:Core
Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Comments
kibanamachine
added
the
failed-test
A test failure on a tracked branch, potentially flaky-test
label
Jan 2, 2023
kibanamachine
added
the
Team:Core
Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
label
Jan 2, 2023
Pinging @elastic/kibana-core (Team:Core) |
New failure: CI Build - main |
New failure: CI Build - main |
May be caused by / related to #147371 |
New failure: CI Build - main |
Skipped main: 1c3dc4a |
Related elastic/elasticsearch#92677 |
jloleysens
added a commit
that referenced
this issue
Jan 9, 2023
Closes #148258 Closes #148263 Related: elastic/elasticsearch#92677 --- Did not test in the flaky test runner (looks like we cannot run Jest integration tests there?), ran locally 5 times without failures.
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
Team:Core
Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
A test failed on a tracked branch
First failure: CI Build - main
The text was updated successfully, but these errors were encountered: