Skip to content

Isolate test landing locks per workspace (knit) - #258

Merged
marc-merino merged 1 commit into
mainfrom
knit/isolate-test-landing-locks-per-workspace
Oct 12, 2026
Merged

marc-merino merged 1 commit into
mainfrom
knit/isolate-test-landing-locks-per-workspace

Conversation

@marc-merino

@marc-merino marc-merino commented Oct 12, 2026 •

Copy link
Copy Markdown
Collaborator

Knit Bundle

View bundle

This PR is part of Knit bundle isolate-test-landing-locks-per-workspace.

See the other review objects in this bundle:

Bundle id: isolate-test-landing-locks-per-workspace
Bundle title: Isolate test landing locks per workspace

… paths

Windows CI failed in three ways: parallel tests that share project `demo`
grabbed the same landing ownership lock in the shared temp directory
(`os error 80` while another test held it); the run checkout directory
under `<run>.run.checkouts/<64-character hash>` grew past Windows' path
limit (`fatal: '$GIT_DIR' too big'`); and the live-output streaming test
gave `sh` five seconds to start, which Windows runners regularly miss.

The test harness now gives every spawned knit process a temp directory
private to its workspace (TMP/TEMP/TMPDIR keyed by cwd), so landing locks
are shared only inside a single test; revert_landed's local wrappers for
the same problem fold back into the harness. Run checkout directories use
a twelve-character hash prefix, like plan fingerprints already do. The
streaming test's deadline rises to thirty seconds; the step's own timeout
still bounds the command.

Knit-Group: kg_20261012_bbe991
Knit-Bundle: isolate-test-landing-locks-per-workspace
@marc-merino
marc-merino merged commit 64a4455 into main Oct 12, 2026
7 checks passed
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