-
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/integration_tests - migration from 7.7.2-xpack with 100k objects copies all the document of the previous index to the new one #96895
Comments
Pinging @elastic/kibana-core (Team:Core) |
After we cut the 7.13 branch this test started failing with:
It's unclear what might be causing this, but the test is reliant on the version and was consistently failing in 7.13, so I only skipped there. CC @rudolf Skipped 7.13: 2b57ef3 |
New failure: Jenkins Build |
@spalger Just checkout'ed the Do you know if anything on CI may be causing that? Of course we don't have an usable stack trace, so that doesn't help a bit about where/how exactly the error did happen. The only notable difference between @delvedor Is there any differences in the transport layer between these two versions? Was any library bumped between those? |
Looking at the extended logs in Jenkins, it looks like a Cross-origin issue? 🤔
|
@pgayvallet no differences. |
@pgayvallet want to try that in a PR that unskips this test? If it's not reproducible in a PR then I'm good moving forward with un-skipping. Otherwise we'll have something we can add additional debug logging to to figure out what's going on. |
I'm wondering why |
Unfortunately Jest has no concept of what a server-side test is, we could use different config files for server/browser tests but for now all tests extend the base config which sets the Jest env to |
New failure: Jenkins Build |
New failure: Jenkins Build |
Also skipping in master as there are quite a few failures here. master: a105c7a |
This test started to failed again and looks flaky. I'm skipping it for now. It failed for example at #15905
master/8.0: f21c7e1 |
A test failed on a tracked branch
First failure: Jenkins Build
The text was updated successfully, but these errors were encountered: