Skip to content

Regular "BusyExecIdle after 200 milliseconds delay" CI failures #2831

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

Closed
jnm2 opened this issue Apr 27, 2018 · 1 comment
Closed

Regular "BusyExecIdle after 200 milliseconds delay" CI failures #2831

jnm2 opened this issue Apr 27, 2018 · 1 comment
Assignees
Milestone

Comments

@jnm2
Copy link
Contributor

jnm2 commented Apr 27, 2018

This is responsible for the last couple dozen times I read through the AppVeyor logs to figure out why a branch was failing to build. Always seems to be net35.

1) Failed : NUnit.Framework.Internal.Execution.TestWorkerTests.BusyExecuteIdleEventsCalledInSequence
  Expected: "BusyExecIdle" after 200 milliseconds delay
  But was:  <string.Empty>
   at NUnit.Framework.Internal.Execution.TestWorkerTests.BusyExecuteIdleEventsCalledInSequence() in C:\projects\nunit\src\NUnitFramework\tests\Internal\TestWorkerTests.cs:line 67

Can we change this to 10_000? If it succeeds it's instantaneous. If it fails, all we care about is not hanging for minutes on end.

@rprouse
Copy link
Member

rprouse commented Apr 27, 2018

Sure, go for it.

@jnm2 jnm2 self-assigned this Apr 28, 2018
@jnm2 jnm2 added this to the 3.11 milestone Apr 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants