-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[jest] use circus runner for the integration tests #102782
[jest] use circus runner for the integration tests #102782
Conversation
// prevents the server to respond | ||
await delay(30000); | ||
return res.ok({ body: 'ok' }); | ||
const done = new Promise<void>((resolve) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
promise + callback style API are not supported simultaneously jestjs/jest#10529
So I didn't migrate core unit tests to circus
.
Pinging @elastic/kibana-operations (Team:Operations) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@elasticmachine merge upstream |
…s' into use-circus-for-intergration-tests
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: |
* use circus runner for integration tests * do not use done callback. jestjs/jest#10529 * fix type error
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
…102948) * [jest] use circus runner for the integration tests (#102782) * use circus runner for integration tests * do not use done callback. jestjs/jest#10529 * fix type error * disable reporting for so 100k migration Co-authored-by: Mikhail Shustov <[email protected]>
Summary
I spent a lot of time debugging
Jest did not exit one second after the test run has completed
in my integration tests. It’s turned out an exception, thrown from theafterAll
lifecycle, interrupts the cleanup logic, but didn't appear in the logs.It seems to be a jest problem, that can be fixed by switching to
jest-circus/runner
.Note, that
jest-circus/runner
will be the default runner fromjest@v27
. We will have to fix otherjasmine2
occurrences in the codebase later.