parallel even with parallel disabled
See original GitHub issueoriginal report
I have set
parallelExecution in Test := false,
parallelExecution in IntegrationTest := false,
testForkedParallel in Test := false,
testForkedParallel in IntegrationTest := false,
(this is actually environment specific, i.e. disable parallel runs on travis, but allow locally)
but ScalaTest WordSpecs that have the ParallelTestExecution
mixin are still running out of order and apparently in parallel. e.g. https://travis-ci.org/ensime/ensime-server/builds/52494180
Issue Analytics
- State:
- Created 9 years ago
- Reactions:3
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Enable Parallel DML Mode
When parallel DML is disabled, no DML is executed in parallel even if the PARALLEL hint is used.
Read more >Why parallel sessions are created even when i disable ...
When parallel DML is disabled, no DML will be executed in parallel even if the PARALLEL hint is used.
Read more >Parallel DML - Oracle Parallel Processing [Book] - O'Reilly
You can execute parallel DDL statements and parallel SELECT statements in a session, regardless of whether parallel DML is enabled or disabled.
Read more >How can I disable parallel queries in PostgreSQL?
So to disable the parallel query planning use, SET max_parallel_workers_per_gather = 0;. You can see that here, same query,
Read more >Disabling parallel builds on solution level - MSDN - Microsoft
documents, that "A value of 0 causes all available processors to be utilized". With that setting projects themselves are still build in parallel ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Aah, cool thanks! It seems bizarre that I have to explicitly disable an experimental feature.
The experimental part I think is the fact that you can tweak the task parallelism within a single command execution.