Two checks failed tonight on timing races in mesh-sdk's TypeScript tests under load (the checker's machines): L2's at 20:29 (test/standing.test.ts: a recovery said before the retirement) and the capacity group's at ~21:30 (test/retire.test.ts:302 'an addition acts on the first pass'). Both were hidden as a passing line by the old verdict (issue 1901).
The kind fixed in both files: a test asserted that the loop had or had not acted by a wall-clock moment, or cleared state the running loop reads. Each test now waits on the attempt count or measures the gap it claims; L2's holdsErrFor fix is included (3a095a6), so the two branches agree. Test-only: no SDK source changed, no new test function.
Proved: the reviewer's mutant (a success not resetting an unannounced run) now fails 3/3 (it passed at the first head); a second mutant announcing on the first failure fails too. Unloaded: 55/55 pass.
Quick fix: retry flaky tests. Thorough fix (chosen): remove the clock assumptions in the whole file pair.
No try: this pull request's check is its only run.
Two checks failed tonight on timing races in mesh-sdk's TypeScript tests under load (the checker's machines): L2's at 20:29 (test/standing.test.ts: a recovery said before the retirement) and the capacity group's at ~21:30 (test/retire.test.ts:302 'an addition acts on the first pass'). Both were hidden as a passing line by the old verdict (issue 1901).
The kind fixed in both files: a test asserted that the loop had or had not acted by a wall-clock moment, or cleared state the running loop reads. Each test now waits on the attempt count or measures the gap it claims; L2's holdsErrFor fix is included (3a095a6), so the two branches agree. Test-only: no SDK source changed, no new test function.
Proved: the reviewer's mutant (a success not resetting an unannounced run) now fails 3/3 (it passed at the first head); a second mutant announcing on the first failure fails too. Unloaded: 55/55 pass.
Quick fix: retry flaky tests. Thorough fix (chosen): remove the clock assumptions in the whole file pair.
No try: this pull request's check is its only run.
Reviewed-by: review-standing@shanks at 18e541c1badca3108249c1c320d2d35bac4c5d82
mesh/check pass 18e541c1badc on 7187beaf042b | carried from 2cbe21937153 | a compiled program is not refused: mesh-build-node reported no programs | u…
Deliverynovox/mesh-sdk@18e541c1badc — merged since 2026-10-26T20:58:47Z
Source — source.main moved to novox/mesh-sdk@7187beaf04. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.
Transitions
2026-10-26 20:57 (new) → proposed (announced): novox/mesh-sdk#101's head announced
2026-10-26 20:58 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
2026-10-26 20:58 ready → merged (merged): on the trunk its modules follow: merged there
The commit's note under refs/notes/mesh-plan keeps every transition of this change up to its merge: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-sdk@18e541c1badc` — **merged** since 2026-10-26T20:58:47Z
**Source** — source.main moved to novox/mesh-sdk@7187beaf042b. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves.
**Transitions**
- 2026-10-26 20:57 (new) → proposed (announced): novox/mesh-sdk#101's head announced
- 2026-10-26 20:58 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
- 2026-10-26 20:58 ready → merged (merged): on the trunk its modules follow: merged there
The commit's note under `refs/notes/mesh-plan` keeps every transition of this change up to its merge: `git log --notes=mesh-plan`.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Two checks failed tonight on timing races in mesh-sdk's TypeScript tests under load (the checker's machines): L2's at 20:29 (test/standing.test.ts: a recovery said before the retirement) and the capacity group's at ~21:30 (test/retire.test.ts:302 'an addition acts on the first pass'). Both were hidden as a passing line by the old verdict (issue 1901).
The kind fixed in both files: a test asserted that the loop had or had not acted by a wall-clock moment, or cleared state the running loop reads. Each test now waits on the attempt count or measures the gap it claims; L2's holdsErrFor fix is included (
3a095a6), so the two branches agree. Test-only: no SDK source changed, no new test function.Proved: the reviewer's mutant (a success not resetting an unannounced run) now fails 3/3 (it passed at the first head); a second mutant announcing on the first failure fails too. Unloaded: 55/55 pass.
Quick fix: retry flaky tests. Thorough fix (chosen): remove the clock assumptions in the whole file pair.
No try: this pull request's check is its only run.
Reviewed-by: review-standing@shanks at
18e541c1baDelivery
novox/mesh-sdk@18e541c1badc— merged since 2026-10-26T20:58:47ZSource — source.main moved to novox/mesh-sdk@7187beaf04. Whether it reached the machines is
mesh-delivery-view's, derived fromsource.main, the wants and the haves.Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition of this change up to its merge:git log --notes=mesh-plan.