stage2-olean-test
Diagnose a spurious stage1 test failure caused by olean-persisted compiler changes. Use when a stage1 test fails unexpectedly and the change adds or modifies an environment extension or other information persisted into .olean files.
来源信息
- 仓库
- leanprover/lean4
- 最近来源活动
- 2026年6月10日 11:48
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 9,551
- 分支
- 1,044
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- stage2-olean-test
- description
- Diagnose a spurious stage1 test failure caused by olean-persisted compiler changes. Use when a stage1 test fails unexpectedly and the change adds or modifies an environment extension or other information persisted into .olean files.
- allowed-tools
- Bash, Read
# Stage2 Is Required for Changes to Olean-Persisted Compiler Information
When a change alters information that is *persisted into `.olean` files* (e.g. a new or changed
environment extension that the compiler reads back), a stage1 test run can fail spuriously: stage1's
`src/` (including `Init`) is compiled by the **stage0** compiler, which lacks the change, so the
stage1 `lean` binary imports oleans that predate the change. In that situation the relevant tests
must be run against **stage2** instead, where the new compiler compiles everything consistently.
So: on a test failure, if the change depends on changed olean information, test stage2 instead.
## Procedure
Building stage2 is expensive, so **confirm with the user before switching to a stage2 build.**
For the actual build/test commands (`make stage2`, `clean-stdlib`, per-module Lake builds, and
running tests against stage2), use the **`stage2-build`** skill.
在 GitHub 查看