Skip to content

D217 — a platform test never waits on the machine's end-to-end lock - #393

Merged
napkinstack-agent[bot] merged 1 commit into
mainfrom
tests-own-e2e-lock
Nov 14, 2026
Merged

napkinstack-agent[bot] merged 1 commit into
mainfrom
tests-own-e2e-lock

Conversation

@napkinstack-agent

Copy link
Copy Markdown
Contributor

Why

The platform suite hung, intermittently, at the same test: test_evidence.py starts real end-to-end runs, which take the machine's end-to-end lock ($XDG_RUNTIME_DIR/nstack-e2e.lock, one run at a time). When another project on the workstation was running its own end-to-end tests, rightly holding that lock, the suite waited for it, for many minutes.

What

platform/tests/conftest.py: an autouse fixture gives every test its own XDG_RUNTIME_DIR (mode 700). No test takes or waits on the machine's lock; the lock's own tests already set theirs.

Checks

  • Seen red first: under the held lock, test_evidence.py hung until timeout. With this change, under the same held lock, it passes: 78 tests in 5 s.
  • uv run bash platform/tests/run.sh: OK (below).

Register row D217. Test infrastructure only; nothing a project receives changes.

🤖 Generated with Claude Code

test_evidence.py starts real end-to-end runs, which take the machine's lock
($XDG_RUNTIME_DIR/nstack-e2e.lock). While another project ran its own end-to-end tests, the
platform suite hung there. Every test now has a runtime folder of its own.

Agent-Session: nstack-os-d217
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@napkinstack-agent
napkinstack-agent Bot merged commit 6da4c72 into main Nov 14, 2026
3 checks passed
@napkinstack-agent
napkinstack-agent Bot deleted the tests-own-e2e-lock branch November 14, 2026 15:06
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