Skip to content

docs: TLA+ full-verification run guide#14

Open
hooyao wants to merge 1 commit intomainfrom
docs-tla-full-verification-guide
Open

docs: TLA+ full-verification run guide#14
hooyao wants to merge 1 commit intomainfrom
docs-tla-full-verification-guide

Conversation

@hooyao
Copy link
Copy Markdown
Owner

@hooyao hooyao commented May 5, 2026

Summary

Adds tla/RUN_FULL_VERIFICATION.md — a self-contained run book for executing the full TLA+ suite on a high-RAM workstation.

CI only runs RamDiskSystem_Minimal.cfg (~12 min). The larger configs (Medium, Standard, Stress) need 10–60 GB RAM and many hours of wall-clock time, so they don't belong on CI but the runner instructions should still live in the repo.

The guide covers:

  • Which specs / configs to run, in cheapest-first order
  • Exact TLC invocation (must be run from the tla/ directory; -Xmx tuning; nohup / tmux pattern for the multi-hour runs)
  • Resource estimates per config
  • The KernelCcCache sanity pair (must-pass + must-fail-deterministically)
  • What to report back; what not to do (don't shrink configs to make them pass, don't disable invariants, don't run Standard and Stress in parallel)

Test plan

  • Markdown renders cleanly on GitHub
  • Used by Claude Code on a separate workstation to drive the full run

🤖 Generated with Claude Code

Adds tla/RUN_FULL_VERIFICATION.md, a self-contained run book that takes a
fresh runner from "I have the repo and Java" to "all configs verified".

Covers:
  - Which specs / configs to run, in cheapest-first order (Minimal smoke ->
    Medium -> Standard ~5h -> Stress optional)
  - Exact TLC invocation (must run from tla/ directory; -Xmx tuning;
    nohup / tmux pattern for the long ones)
  - Resource estimates (Standard needs ~60 GB RAM; Stress can OOM)
  - The KernelCcCache sanity pair (must-pass and must-fail-deterministically)
  - What to report back; what NOT to do (don't shrink configs to make them
    pass, don't disable invariants, don't run Standard and Stress in parallel)

CI only runs Minimal (~12 min). The larger configs need a dedicated machine,
so this guide lives next to the specs and tells whoever runs them what's
expected.

Co-Authored-By: Claude Opus 4.7 (1M context) <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