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 multiple versions available, including 4.8.0, 4.4.0, 4.3.1, 4.2.0, 4.0.0, and 3.2.0."],["The documentation includes classes for testing, such as `FakeClock`, which allows for manually specified times and increments, implementing the `IClock` interface."],["`FakeScheduler`, an experimental class, is designed to work with `FakeClock` and implements the `IScheduler` interface."],["`FakeScheduler.SchedulerTimeoutException` is a specific exception to indicate a timeout within the scheduler."],["`NoOpScheduler` is an `IScheduler` implementation that doesn't introduce delays, used for tests not focused on precise timing."]]],[]]
