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.

Sign up for GitHub

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

Jump to bottom

Parallel non-io tests #139

Closed
indutny opened this issue Dec 10, 2014 · 1 comment
Closed

Parallel non-io tests #139

indutny opened this issue Dec 10, 2014 · 1 comment
Assignees
@indutny
Milestone
1.0.0

Comments

@indutny
Copy link
Member

indutny commented Dec 10, 2014

Move some tests to io folder to make simple tests run in parallel.
@indutny indutny self-assigned this Dec 10, 2014
@indutny indutny added this to the v1.0.0 milestone Dec 10, 2014
@indutny indutny mentioned this issue Dec 16, 2014
Closed
indutny added a commit that referenced this issue Dec 17, 2014
@indutny
test: split test in parallel/sequential
0e19476 
Reviewed-By: Ben Noordhuis <[email protected]>
PR-URL: #172
Fix: #139
indutny added a commit that referenced this issue Dec 17, 2014
@indutny
test: run tests in parallel, common improvements
b7d2478 
* Allow running tests in mixed parallel/sequential modes
* Add -J flag for running tests on all available CPUs
* Support TEST_THREAD_ID in test/common.js and use it for tmpDir and PORT
* make: use -J flag

Reviewed-By: Ben Noordhuis <[email protected]>
PR-URL: #172
Fix: #139
@chrisdickinson
Copy link
Contributor

This seems to have been addressed by #172. Closing!

kunalspathak referenced this issue in nodejs/node-chakracore Dec 7, 2015
@kunalspathak
chakrashim: Remove option to build with 'chakra'
1f2ab92 
chnext will only be able to built using chakracore and not chakra.
Removed msi/sdk changes for chakrashim that were mistakenly present in
chnext branch. They should be present in chnext-msi branch.

Fixes : #139
@sushi90 sushi90 mentioned this issue Aug 24, 2016
Closed
@adelphes adelphes mentioned this issue Oct 31, 2016
Closed
boingoing pushed a commit to boingoing/node that referenced this issue Apr 6, 2017
@digitalinfinity
napi, test: Fix eslint errors (nodejs#139)
e61a100 
Fixes eslint errors in the test js files
Generally trivial mechanical transformation
@gaurav-moonfroglabs gaurav-moonfroglabs mentioned this issue Jul 24, 2017
Closed
This was referenced Jan 21, 2020
Open
Open
@snyk-bot snyk-bot mentioned this issue Oct 22, 2020
Open
@snyk-bot snyk-bot mentioned this issue Jun 17, 2021
Open
@snyk-bot snyk-bot mentioned this issue Jun 30, 2021
Open
@snyk-bot snyk-bot mentioned this issue Sep 4, 2021
Open
@RoeeOren RoeeOren mentioned this issue Oct 5, 2022
Open
@InfiniteLove2020 InfiniteLove2020 mentioned this issue Mar 23, 2023
Open
@snyk-bot snyk-bot mentioned this issue Apr 24, 2023
Open
@aborovsky aborovsky mentioned this issue Aug 24, 2023
Closed
@RoeeOren RoeeOren mentioned this issue Nov 28, 2023
Open
@AyushG3112 AyushG3112 mentioned this issue Nov 30, 2023
Open
@thakursachin467 thakursachin467 mentioned this issue Nov 30, 2023
Open
@RoeeOren RoeeOren mentioned this issue Nov 30, 2023
Open
@GregorFendt GregorFendt mentioned this issue Nov 30, 2023
Open
@dewaynesmith3711 dewaynesmith3711 mentioned this issue Nov 30, 2023
Open
@BryanLaura BryanLaura mentioned this issue Nov 30, 2023
Open
@dannybrown13 dannybrown13 mentioned this issue Nov 30, 2023
Open
@ambai ambai mentioned this issue Nov 30, 2023
Open
@dewaynesmith3711 dewaynesmith3711 mentioned this issue Nov 30, 2023
Open
This was referenced Nov 30, 2023
Open
Open
Open
Open
@BryanLaura BryanLaura mentioned this issue Nov 30, 2023
Open
@dewaynesmith3711 dewaynesmith3711 mentioned this issue Nov 30, 2023
Open
@xphillyx xphillyx mentioned this issue Nov 30, 2023
Open
@AshdonG AshdonG mentioned this issue Dec 1, 2023
Open
@sirinartk sirinartk mentioned this issue Dec 1, 2023
Open
@ZRDK ZRDK mentioned this issue Dec 1, 2023
Open
@terrorizer1980 terrorizer1980 mentioned this issue Dec 1, 2023
Open
@ambai ambai mentioned this issue Dec 1, 2023
Open
@pratapadi pratapadi mentioned this issue Dec 1, 2023
Open
@dannybrown13 dannybrown13 mentioned this issue Dec 1, 2023
Open
@BryanLaura BryanLaura mentioned this issue Dec 1, 2023
Open
@Verdinjoshua26 Verdinjoshua26 mentioned this issue Dec 1, 2023
Open
@Bhanditz Bhanditz mentioned this issue Dec 1, 2023
Open
@adamlaska adamlaska mentioned this issue Dec 1, 2023
Open
@wedataintelligence wedataintelligence mentioned this issue Dec 1, 2023
Open
@adamlaska adamlaska mentioned this issue Dec 1, 2023
Open
@kaocher82 kaocher82 mentioned this issue Dec 1, 2023
Open
@terrorizer1980 terrorizer1980 mentioned this issue Dec 1, 2023
Open
@Supermajestcd Supermajestcd mentioned this issue Dec 1, 2023
Open
@ajesse11x ajesse11x mentioned this issue Dec 1, 2023
Open
@timzwit timzwit mentioned this issue Apr 29, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@indutny indutny

Labels
None yet
Projects
None yet
Milestone
1.0.0
Development

No branches or pull requests
3 participants
@chrisdickinson @piscisaureus @indutny