-
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
[ci] Run Jest tests in parallel #115687
[ci] Run Jest tests in parallel #115687
Conversation
d81d894
to
9fb0aff
Compare
15cd15b
to
e75db5a
Compare
14707c6
to
b3585c7
Compare
a29c15a
to
871b62f
Compare
0e2e005
to
4f8847f
Compare
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
140db39
to
868cd6d
Compare
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. |
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
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. |
This reverts commit 237d68d.
* [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>
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