[ci] Run Jest tests in parallel #115687
Merged
[ci] Run Jest tests in parallel #115687
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
tylersmalley
force-pushed
the
split-jest
branch
from
d81d894
to
9fb0aff
Compare
tylersmalley
force-pushed
the
split-jest
branch
9 times, most recently
from
15cd15b
to
e75db5a
Compare
tylersmalley
changed the title
tylersmalley
force-pushed
the
split-jest
branch
4 times, most recently
from
14707c6
to
b3585c7
Compare
tylersmalley
commented
Oct 20, 2021
tylersmalley
force-pushed
the
split-jest
branch
from
a29c15a
to
871b62f
Compare
tylersmalley
force-pushed
the
split-jest
branch
3 times, most recently
from
0e2e005
to
4f8847f
Compare
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
tylersmalley
force-pushed
the
split-jest
branch
from
140db39
to
868cd6d
Compare
tylersmalley
added
Team:Operations
|
Pinging @elastic/kibana-operations (Team:Operations) |
|
@elasticmachine merge upstream |
|
I think that there are too many JUnit artifacts being produced at the moment, and we maybe need to figure out something with that. This one has over 1000 artifacts! |
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
|
@brianseeders, explicitly disabled code coverage. When we re-enable we can overwrite the output location so we can select what to be uploaded. |
brianseeders
reviewed
Nov 1, 2021
brianseeders
approved these changes
Nov 1, 2021
added 2 commits
November 1, 2021 11:44
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
spalger
reviewed
Nov 1, 2021
spalger
approved these changes
Nov 1, 2021
vadimkibana
approved these changes
Nov 2, 2021
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
💚 Build Succeeded
Metrics [docs]
History
To update your PR or re-run it, just comment with: |
|
Merging this ahead of the pending reviews as they are for teams triggered by the removal of unused Jest config files. Feel free to ping me if there are concerns. |
tylersmalley
pushed a commit
that referenced
this pull request
Nov 2, 2021
This reverts commit 237d68d.
tylersmalley
pushed a commit
to tylersmalley/kibana
that referenced
this pull request
Nov 2, 2021
* [ci] Run Jest tests in parallel Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co> * Disable coverage Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co> * Make hourly match prs Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co> * Update timeout Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co> * mock process.execArgv so that it is consistent * Remove comment Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co> Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: spalger <spalger@users.noreply.github.com>
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.
We have run into issues with parallelizing Jest tests using its built-in workers. This moves us to run the tests in-band on separate smaller machines. This reduces the overall cost of the Jest tests, isolates Jest tests to plugins, and prepares us for code-coverage reporting on PR's.
Jest configurations with no matching test files were removed as to not take needless setup time and further skew the split.
Resource comparison:
Current:
c2-16 for 90 minutes
1440 core minutes
Split:
c2-4 for 305 minutes
1220 core minutes
Skipped tests suites tracked in #115881