Skip to content
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

Closed
boneskull opened this issue Jan 18, 2018 · 4 comments
Closed
Labels
nice to have enhancement proposal of low priority type: chore generally involving deps, tooling, configuration, etc.

Comments

@boneskull
Copy link
Member

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...

@boneskull boneskull added the type: chore generally involving deps, tooling, configuration, etc. label Jan 18, 2018
@boneskull boneskull self-assigned this Jan 18, 2018
@boneskull
Copy link
Member Author

concurrently doesn't seem to allow a limit on how many processes to execute at once, which is problematic, since some just hang.

@boneskull boneskull removed their assignment Mar 23, 2018
@boneskull boneskull added nice to have enhancement proposal of low priority status: accepting prs Mocha can use your help with this one! and removed status: accepting prs Mocha can use your help with this one! labels Mar 23, 2018
@boneskull boneskull reopened this Mar 23, 2018
@boneskull
Copy link
Member Author

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:

image

image

My branch is here which I'll leave up for awhile, so you can see what I was trying to do.

@boneskull boneskull added the status: accepting prs Mocha can use your help with this one! label Mar 23, 2018
@plroebuck
Copy link
Contributor

You try setting process.env.FORCE_COLOR = 'true' first?

@boneskull boneskull added stale this has been inactive for a while... and removed stale this has been inactive for a while... labels Feb 28, 2020
@juergba
Copy link
Member

juergba commented Jul 2, 2021

GH actions is running our CI tests in parallel, or concurrently?
Closing due to inactivity.

@juergba juergba closed this as completed Jul 2, 2021
@juergba juergba removed the status: accepting prs Mocha can use your help with this one! label Jul 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
nice to have enhancement proposal of low priority type: chore generally involving deps, tooling, configuration, etc.
Projects
None yet
Development

No branches or pull requests

3 participants