-
-
Notifications
You must be signed in to change notification settings - Fork 731
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
XUnit2Runner doesn't respect ParallelismOption.None
#2039
Labels
Milestone
Comments
I will have a PR for this shortly |
kcamp
added a commit
to kcamp/cake
that referenced
this issue
Feb 14, 2018
…t specifications of ParallelismOption.None
kcamp
added a commit
to kcamp/cake
that referenced
this issue
Feb 27, 2018
…t specifications of ParallelismOption.None
kcamp
added a commit
to kcamp/cake
that referenced
this issue
Mar 8, 2018
…t specifications of ParallelismOption.None
devlead
pushed a commit
to kcamp/cake
that referenced
this issue
Mar 13, 2018
…t specifications of ParallelismOption.None
Fixed by #2040 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What You Are Seeing?
XUnit2 is not respecting
ParallelismOption.None
What is Expected?
The XUnit tool command should include the
-parallel none
when it's specified.What version of Cake are you using?
0.25
Are you running on a 32 or 64 bit system?
64
What environment are you running on? Windows? Linux? Mac?
Windows
Are you running on a CI Server? If so, which one?
N/A
How Did You Get This To Happen? (Steps to Reproduce)
In consideration of this sample set of tests..
When running this assembly with the task (following) I would expect the elapsed time of the tests to be 15 seconds.
Instead, it executes in ~10 seconds, indicating some degree of parallelism is at play.
Reading the docs at https://xunit.github.io/docs/running-tests-in-parallel.html
I think this last bit (defaulting to
collections
)is where our bug is coming into play; by suppressing the-parallel none
, we're accepting the runner default.Running that same set of tests again, manually from the CLI (below) to explicitly add the
none
flag gives execution time of ~15 seconds, as expected.Output Log
The text was updated successfully, but these errors were encountered: