-
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.x-pack/test_utils/jest/integration_tests - example integration test with kbn server should have started new platform server correctly #32795
Comments
Pinging @elastic/kibana-test-triage |
New failure: Jenkins Build |
Fixed by #32803 |
New failure: Jenkins Build |
New failure: Jenkins Build |
|
I have been looking into some things we can do to make sure that the server does not continue to run if the
@spalger What do you think about these options? |
@njd5475 I definitely think that failures in startup should be caught by try...catch and trigger a shutdown of already started components, but the primary issue I see is that until there is success we can't trigger a shutdown if jest aborts the test due to timeout. for this we'll need something like an AbortController, or a cancelable promise, so we can shutdown the servers when they take too long to start up. |
Pinging @elastic/kibana-platform |
Will reopen if it fails again. |
A test failed on a tracked branch
First failure: Jenkins Build
The text was updated successfully, but these errors were encountered: