Closed
Conversation
Collaborator
|
Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/52145/ |
5da6784 to
908eea2
Compare
Member
|
@liuxingbaoyu I haven't seen the failure for a while: do we still need this? |
Member
Author
|
This happens quite often when I test coverage locally, but it really doesn't exist on CI. This should have been resolved in another PR, but that one is more complicated. This PR should mostly be fine, I tend to keep a JEST running, what do you think? |
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
I suspect the ci failure in the main branch has something to do with the
worker_threadsused byjest-light-runner.I'm worried it will get worse in the future.
Let's keep
jest-runneravailable as a backup.