Yes, the only system/real-time timeout is a progress one, wherein if nothing happens for ten minutes we assume the simulation has locked up. Hitting this is indicative of a bug, and the timeout is so long that no realistic system variability could trigger it.
> On 7 Dec 2023, at 14:56, Brandon Williams <dri...@gmail.com> wrote: > > On Thu, Dec 7, 2023 at 8:50 AM Alex Petrov <al...@coffeenco.de> wrote: >>> I've noticed many "sleeps" in the tests - is it possible with simulation >>> tests to artificially move the clock forward by, say, 5 seconds instead of >>> sleeping just to test, for example whether TTL works?) >> >> Yes, simulator will skip the sleep and do a simulated sleep with a simulated >> clock instead. > > Since it uses an artificial clock, does this mean that the simulator > is also impervious to timeouts caused by the underlying environment? > > Kind Regards, > Brandon
