[ci] run unit tests in series again #141481
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
spalger
force-pushed
the
run-jest-tests-in-series
branch
from
07ddea2 to
a6ec1da
Compare
spalger
force-pushed
the
run-jest-tests-in-series
branch
from
c121b29 to
3fff683
Compare
spalger
force-pushed
the
run-jest-tests-in-series
branch
from
3fff683 to
e54db2f
Compare
💚 Build Succeeded
Metrics [docs]
History
To update your PR or re-run it, just comment with: |
spalger
added
Team:Operations
|
Pinging @elastic/kibana-operations (Team:Operations) |
tylersmalley
approved these changes
Sep 23, 2022
sorenlouv
approved these changes
Sep 23, 2022
kibanamachine
added
v8.6.0
backport:skip
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Assists with #141477
@elastic/apm-ui folks, I needed to skip a test to make this work. More details here: #141543
Reduce the concurrency of jest unit tests back to 1 by running tests in band. It seems like
react-dom/test-utilsis constantly breaking Jest workers by trying to fire click events after jsdom is torn-down, leading to exceptions and flaky failures.In researching solutions for #115307 we identified that CPU load leads to this race condition triggering more often, so I'm hoping that reducing the concurrency of our tests can help us reduce the annoyance of flaky Jest tests until jestjs/jest#12670 is resolved or we find some other workaround.