Exception designed not to be caught by tests (which may deliberately expect a timeout of another kind, for example).
This exception indicates that the scheduler timed out either in simulated time (e.g. a busy loop with a condition
never being satisfied) or in wall time (e.g. user code was waiting for a task which was never going to complete, due
to a deadlock).
An implementation of IScheduler that doesn't actually delay. This is useful for tests
which aren't interested in precise timing, but just want to be able to use a scheduler.
For more fine-grained control, use FakeScheduler.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-04-17 UTC."],[[["The latest version of the documentation is 4.10.0, with the current page focused on version 4.8.0."],["The `FakeClock` class allows for manually specifying and incrementing times, implementing the `IClock` interface."],["The `FakeScheduler` class, which is still considered experimental, works with `FakeClock` to simulate time."],["The `FakeScheduler.SchedulerTimeoutException` class indicates that the scheduler timed out either in simulated or wall time and is designed not to be caught by tests."],["The `NoOpScheduler` class is an implementation of `IScheduler` that does not introduce delays, for tests not concerned with precise timing."]]],[]]
