Skip to content

test: skip concurrent directory ops until #29 lands - #79

Merged
mattmattox merged 1 commit into
mainfrom
claude/skip-dir-ops-until-29
Nov 13, 2026
Merged

mattmattox merged 1 commit into
mainfrom
claude/skip-dir-ops-until-29

Conversation

@mattmattox

Copy link
Copy Markdown
Contributor

TestMultiNodeConcurrentDirectoryOps loses a directory entry because two nodes can both hold the root directory lock (#29). It failed 3 main CI runs today (ad55520, #77's PR run, 5c7c6c4), so main needs a rerun every second or third run.

This skips the Go test and its Docker and VM variants, following the existing #29 snapshot skips. The Docker and VM variants fail the same way: Docker on #24 (node1_1.txt missing on both nodes) and VM on #59 (files missing on both VMs). Docker CI already skipped this test through SKIP_CONCURRENT_TESTS; local Docker runs now skip it too.

#29's branch keeps the test enabled as its proof. Remove these skips when #29 merges.

🤖 Generated with Claude Code

Two nodes can both hold the root directory lock and lose an entry,
which fails this test in about one of every two or three main CI runs.
Skip it in the Go, Docker and VM suites until #29 confirms lock claims.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@mattmattox
mattmattox merged commit b3efca0 into main Nov 13, 2026
13 checks passed
mattmattox added a commit that referenced this pull request Nov 13, 2026
#79 skipped TestMultiNodeConcurrentDirectoryOps in the Go, Docker and VM
suites until lock claims are confirmed. This branch confirms them, so the
test runs in all three again, in Docker without the SKIP_CONCURRENT_TESTS gate.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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