Skip to content

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

Description

@jnm2

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions