Title: Support `concurrency` when `--experimental-test-isolation` is set to `'none'` · Issue #55939 · nodejs/node · GitHub
Open Graph Title: Support `concurrency` when `--experimental-test-isolation` is set to `'none'` · Issue #55939 · nodejs/node
X Title: Support `concurrency` when `--experimental-test-isolation` is set to `'none'` · Issue #55939 · nodejs/node
Description: What is the problem this feature will solve? It would be nice to be able to run multiple "workers" when using the none test isolation mode. Today, according to the docs, when --experimental-test-isolation is set to 'none', it implies 1 c...
Open Graph Description: What is the problem this feature will solve? It would be nice to be able to run multiple "workers" when using the none test isolation mode. Today, according to the docs, when --experimental-test-is...
X Description: What is the problem this feature will solve? It would be nice to be able to run multiple "workers" when using the none test isolation mode. Today, according to the docs, when --experiment...
Opengraph URL: https://github.com/nodejs/node/issues/55939
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Support `concurrency` when `--experimental-test-isolation` is set to `'none'`","articleBody":"### What is the problem this feature will solve?\n\nIt would be nice to be able to run multiple \"workers\" when using the `none` test isolation mode.\r\n\r\nToday, according to the docs, when `--experimental-test-isolation` is set to `'none'`, it implies 1 concurrency: https://github.com/nodejs/node/blob/f270462c09ddfd770291a7c8a2cd204b2c63d730/doc/api/cli.md#L2252-L2264\r\n\r\nHowever, `mocha` another test runner that does not isolate tests, does accept a concurrency flag: https://mochajs.org/#parallel-tests\n\n### What is the feature you are proposing to solve the problem?\n\nWe're looking to move off of `jest` because its test module isolation is extremely slow. We love the idea of using the node-native test runner with isolation disabled, instead of adopting another third-party framework like `mocha`.\r\n\r\nHowever, we'd need to write some custom code (e.g., using [`parallel`](https://www.gnu.org/software/parallel/)) to spin up `n` concurrent, isolation-disabled tests to effectively utilize all the cores available on our CI machine.\r\n\r\nThe docs and other recent comments all indicate that when `--experimental-test-isolation` is set to `'none'`, concurrency must be `1`. However, I couldn't find the reasoning in [the original PR](https://github.com/nodejs/node/pull/53927) or [issue](https://github.com/nodejs/node/issues/51548).\r\n\r\nThere's probably a good reason for this but, as someone not intimately familiar with the implementation, it's not obvious to me why we wouldn't be able to run non-isolated tests concurrently, like in `mocha`.\n\n### What alternatives have you considered?\n\nI could probably use a tool like [`parallel`](https://www.gnu.org/software/parallel/) to spin up multiple calls to `node --test`. However, this would require me to also write code to split up all the test files between the parallel runs, etc.","author":{"url":"https://github.com/blimmer","@type":"Person","name":"blimmer"},"datePublished":"2024-11-20T22:08:01Z","url":"https://github.com/nodejs/node/issues/55939"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react-reconciler,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@d5750093facf |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:f54670d3-68e6-40cf-3819-d8c7f2b8bc95 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | CC5A:24555E:EC465E:13AEB8B:6AED4A11 |
| html-safe-nonce | e5c523636ee4c950dc6daa40dc44c4da5d58bca7598be06f410899c7769ef309 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJDQzVBOjI0NTU1RTpFQzQ2NUU6MTNBRUI4Qjo2QUVENEExMSIsInZpc2l0b3JfaWQiOiIyNTA3OTUxNTE0Njg4NzY4NTI5IiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0= |
| visitor-hmac | 512e65d919812591685db080182c2ecfb1094dec86e1d72e24d3d0feb809e0f5 |
| hovercard-subject-tag | issue:2677333920 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/nodejs/node/55939/issue_layout |
| twitter:image | https://opengraph.githubassets.com/301a12c8914fca1b94a9ada9e3e130954d4010bb9c044d108e584c4c2555089f/nodejs/node/issues/55939 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/301a12c8914fca1b94a9ada9e3e130954d4010bb9c044d108e584c4c2555089f/nodejs/node/issues/55939 |
| og:image:alt | What is the problem this feature will solve? It would be nice to be able to run multiple "workers" when using the none test isolation mode. Today, according to the docs, when --experimental-test-is... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | blimmer |
| hostname | github.com |
| expected-hostname | github.com |
| None | 56fb42677ae87ed3e64410323d67980aa65d0485568a7858f874e7edfc6d1c11 |
| turbo-cache-control | no-preview |
| go-import | github.com/nodejs/node git https://github.com/nodejs/node.git |
| octolytics-dimension-user_id | 9950313 |
| octolytics-dimension-user_login | nodejs |
| octolytics-dimension-repository_id | 27193779 |
| octolytics-dimension-repository_nwo | nodejs/node |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 27193779 |
| octolytics-dimension-repository_network_root_nwo | nodejs/node |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 9c9a37e2423ed382cf39f70b5aa4b4858b40a3b0 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width