The provider loop's tests wait on what they mean, not on the clock (issue 1901 note 27)

+48 -27

4 Commits

Author	SHA1	Message	Date
jschoubben	18e541c1ba	The standing test allows 10 ms between the loop's clock and the test's stamp of an announcement mesh/delivery merged: source.main moved to novox/mesh-sdk@7187beaf042b Details mesh/check pass 18e541c1badc on 7187beaf042b \| carried from 2cbe21937153 \| a compiled program is not refused: mesh-build-node reported no programs \| u…	2026-10-26 21:55:46 +01:00
jschoubben	cf930388f9	The standing test's runs last 0.6 of failingAfterMs of clock as well as two attempts, so a success that does not reset a run is caught; the addition test holds a thousand stable passes, so 'first pass' is proved (review of the standing test races)	2026-10-26 21:49:03 +01:00
jschoubben	36ae0c691b	The standing and retirement tests wait on what they mean, not on a slept fraction of a bound: announcements are timed from the clock at the moment they are said, short runs are counted in attempts, an addition is proved by a hold it must not wait for (the second timing race of one kind in a day; issue 1126)	2026-10-26 21:44:06 +01:00
jschoubben	3a095a66be	The standing test keeps c failing alone after its ask is dropped, so its only recovery is its retirement: clearing every failure at once raced the loop's read of the new list under load (issue 1126; the hidden failure of try-1793042418286545971, issue 1901)	2026-10-26 21:33:20 +01:00

The provider loop's tests wait on what they mean, not on the clock (issue 1901 note 27) #101