Skip to content

LAND-3b: train build tells the device run wrote lanes.json by its file time, not a content change - #92

Merged
thejackshelton merged 1 commit into
masterfrom
train-tooling-2
Oct 3, 2026
Merged

thejackshelton merged 1 commit into
masterfrom
train-tooling-2

Conversation

@thejackshelton

Copy link
Copy Markdown
Contributor

What changed

LAND-3b: one fix to #76, found by the train 1 rebuild on 0d04dc0.

train build checked that the device run had rewritten packages/parity/out/lanes.json by asking git whether the file had changed. Position 1 of the rebuild merges #59's PR head (2d47e5d, the position from the earlier build). That head already holds this tree's device run, so the new run wrote byte-identical evidence (iOS 57 / Android 86, all other lanes passing). The build then stopped with "the device run did not rewrite packages/parity/out/lanes.json" although the run had completed. Now deviceRunWrote compares the file's modification time with the time the device step started (one second of slack for filesystem time resolution).

What passed

  • pnpm typecheck: pass.
  • merge-train.test.ts and pr-review.test.ts: 63 pass. The new deviceRunWrote test does not compile against the previous scripts.
  • /tmp/heavy-lease.sh pnpm test on b209a8f: 3624 pass, 1 skipped (the DRAGON_REGEN_CHECK suite), 0 fail.

Changed tests and checks

  • New test only. The check still stops the build when the run did not write the file (an older time, no start time, or NaN). No check is removed.

🤖 Generated with Claude Code

…ication time against the run's start, not by a content change: train 1's rebuilt position 1 merged #59's earlier position, whose lanes.json already held this tree's device run, so the new run wrote identical bytes and the build stopped with 'the device run did not rewrite'. deviceRunWrote is pinned in merge-train.test.ts
@thejackshelton
thejackshelton merged commit 737bcc9 into master Oct 3, 2026
4 checks passed
@thejackshelton
thejackshelton deleted the train-tooling-2 branch October 3, 2026 06:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant