ci(jest): split jest tests to run in multiple shards #3912
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
🦋 Changeset detectedLatest commit: 9381e58 The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Is it possible to hide these shards? It's getting a bit crowded in the checks window |
No idea. I haven't found any docs about it, but I can try random things and see if it works 🤷🏻♀️ |
|
I suppose it's only cluttered for now, we're approaching KAIO, so it'll slim significantly |
gyfchong
approved these changes
Jul 26, 2023
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.
Why
KDS-1641
We write a lot more tests nowadays (which is great!), so it takes much longer to run them in CI, leading to potential timeouts (we currently set GH Actions to time out at 10 minutes).
Eg. https://github.com/cultureamp/kaizen-design-system/actions/runs/5663799519
Using shards(https://jestjs.io/docs/cli#--shard ) we can run multiple GH jobs in parallel, which should save time.
What