-
Notifications
You must be signed in to change notification settings - Fork 471
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
Fixed parallelism is ignored with ProcessBuilder.wait #2117
Comments
Listen to your own words, as you said the important thing already yourself. :-) Besides that, here even when using a Java 21 Azul Zulu JDK to run the tests I indeed get 4 Tests run in parallel only. Maybe your issue - resp. the native code - is doing something like junit-team/junit5#3108 and thus suffering from the same bug that is there. Maybe the work-around I described at junit-team/junit5#3108 (comment) can also work for you if it is a similar problem. 🤷♂️ |
Ack. Is there a way to specify max number of tests running concurrently? I think not but thought I'd check. |
As I said, if it is similar to that issue, you can try my work-around, or also the other options mentioned in that issue's comments |
As it is most likely a JUnit Platform issue if at all, I'm going to close this here. |
Describe the bug
I'd like concurrent testing, but only 4 tests to run at a time. If I set runner.parallel.enabled I get the former. Using .fixed does not fix the latter.
To Reproduce
My SpockConfig.groovy has,
This works when I have basic tests like this.
This does not work when my tests do,
When my tests hit that point, the test framework or the executor (not sure) admits more tests than the fixed(4) limit I tried to specify.
FWIW I'd guess what's happening is that
waitFor
is doing a yield and allowing the executor to run something else until the OS comes back with some I/O.Expected behavior
4 tests are run.
Fixed parallelism of tests should always limit the number of inflight tests.
It seems to currently be too tied to executors and not enough to the test framework actually limiting inflight tests.
Actual behavior
9 tests (all of them) are run.
Java version
Buildtool version
What operating system are you using
Mac
Dependencies
I'd prefer not to share this, let me know if you need it though.
Additional context
No response
The text was updated successfully, but these errors were encountered: