-
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: X-Pack Reporting API Integration Tests.x-pack/test/reporting_api_integration/reporting_and_security/bwc_generation_urls·ts - Reporting APIs BWC report generation urls Pre 6_2 job posted successfully #93354
Comments
New failure: Jenkins Build |
Most recent failure was caused by Chrome aborting all connections because the network list changed, not something the test can really control. |
New failure: Jenkins Build |
Same issue, Chrome aborted all requests mid test. |
New failure: Jenkins Build |
Pinging @elastic/kibana-reporting-services (Team:Reporting Services) |
New failure: Jenkins Build |
New failure: Jenkins Build |
New failure: Jenkins Build |
All the recent test failures are timeouts: Looks like they're only happening on 7.x and 7.14 (and one 7.14 backport), seems these tests have only ever existed in 7.x... I think someone from @elastic/kibana-reporting-services should really take a look at this. Skipped |
New failure: Jenkins Build |
Test is failing because a queued job is not getting claimed (for some reason). There is only 1 report job, and it stays in
|
New failure: Jenkins Build |
New failure: CI Build |
New failure: CI Build |
New failure: CI Build - 7.x |
Skipped in 7.x and 7.15 as well |
This test was hitting issues with Task Manager. I'm not sure, but that could be due to the way the test used es_archiver to load Kibana objects. Those types of problems are resolved in #116528 |
Replacing with: #120192 |
A test failed on a tracked branch
First failure: Jenkins Build
The text was updated successfully, but these errors were encountered: