Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Failing test: Jest Integration Tests.src/core/server/legacy/integration_tests - logging service compatibility uses configured loggers falls back to the root legacy logger otherwise #64482

Closed
kibanamachine opened this issue Apr 25, 2020 · 21 comments
Closed

Failing test: Jest Integration Tests.src/core/server/legacy/integration_tests - logging service compatibility uses configured loggers falls back to the root legacy logger otherwise #64482

kibanamachine opened this issue Apr 25, 2020 · 21 comments
Labels
failed-test A test failure on a tracked branch, potentially flaky-test

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Apr 25, 2020 •
edited
Loading

A test failed on a tracked branch

Timeout - Async callback was not invoked within the 30000ms timeout specified by jest.setTimeout.Error: Timeout - Async callback was not invoked within the 30000ms timeout specified by jest.setTimeout.
    at mapper (/var/lib/jenkins/workspace/elastic+kibana+master/kibana/node_modules/jest-jasmine2/build/queueRunner.js:25:45)
    at promise.then (/var/lib/jenkins/workspace/elastic+kibana+master/kibana/node_modules/jest-jasmine2/build/queueRunner.js:73:41)

First failure: Jenkins Build
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Apr 25, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-test-triage (failed-test)

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@spalger
Copy link
Contributor

spalger commented Apr 26, 2020

These tests started failing once I merged skips for #64382, #64381, #64480, and #64310

Reverted the skips

@spalger spalger closed this as completed Apr 26, 2020
This was referenced Apr 26, 2020
Closed
Closed
Closed
Closed
@kibanamachine kibanamachine reopened this May 16, 2020
@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
failed-test A test failure on a tracked branch, potentially flaky-test
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@tylersmalley @spalger @elasticmachine @kibanamachine