-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
run some tests concurrently where possible; improve package-scripts.js #3209
Comments
concurrently doesn't seem to allow a limit on how many processes to execute at once, which is problematic, since some just hang. |
I'm not seeing any significant speedup on Travis-CI with what I'm doing now, so maybe someone else has a better idea. To be clear: speeding up CI is the goal. However, I am seeing a decent speedup in a local environment, which isn't surprising, given the way we partition the tests on Travis-CI. It's also considerably more difficult to understand what's happening, and way worse on Travis-CI, since there are no colors to help. Here are a couple screenshots: My branch is here which I'll leave up for awhile, so you can see what I was trying to do. |
You try setting |
GH actions is running our CI tests in parallel, or concurrently? |
nps-utils makes this pretty easy.
I've cut a lot of time off of running tests locally using concurrent execution. CI remains to be seen...
The text was updated successfully, but these errors were encountered: