-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Akka.TestKit creation and ActorSystem.Create time-out when system is under load #2331
Comments
Encountered the same issue with NUnit and parameterized tests. A combinatorial test with 3 parameters producing 40 individual tests. Running with ReSharper test runner in VisualStudio. The first 5-6 tests pass while the remainder fail (except the odd one). MSTest explorer results in the same problem.
|
Added #4424 as a work-around for this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Recently I stumbled upon wobbly tests in our build. Investigation showed that the failing test was caused by a time-out in the
TestKitBase.InitializeTest
method. In trying to have a reproducible test-case I ran our tests while also running Prime95. This resulted in a lot of tests failing the failure cases could be split into two distinct cases:and
Since our build runs all of our tests in parallel these two cases actually pop-up in the wild. Inspecting the code I noticed that the
logger-startup-timeout
is configurable. However the timeout inTestKit.InitializeTest
is hard-coded. So my proposal would be to either increase it or make it configurable as well. In case the project also thinks it is a good idea to just increase the time out, I'll be happy to create a pull request for it, ;-).The text was updated successfully, but these errors were encountered: