feat: mcpp test capability batch — isolation, parallel, filter, list, timeout, JSON (0.0.104)#274
Merged
Merged
Conversation
… — nested mcpp no longer segfaults its tools
… checks the disk, not just scanned sources
…leading mid-run Finished banner
…tion, roadmap P1-P6
…ll time 29s -> 3.7s on 49 tests
…uration_ms in JSON
…N records for tooling
…st-effort untimed)
…s, naming exemption note (zh+en)
…lter, list, timeout, json, signal fix)
… with pre-existing scripts)
…antics, documented Windows limitation
Sunrisepeak
added a commit
that referenced
this pull request
Jul 25, 2026
….0.107 (#281) A shared library that declares `soname` is written as bin/libX11.so but records SONAME libX11.so.6. Both the linker resolving a transitive NEEDED and the loader starting a binary look for the alias, never for the plain name — so the alias is a prerequisite of anything that links the library, not a by-product of building it. It was modelled as a standalone ninja edge that nothing depends on, reachable only through `default`. The 0.0.104 test batch (#274) made `mcpp test` pass explicit goal targets so it could isolate per-test compiles, and that silently stopped producing the alias. `mcpp build` and `mcpp run` drive `default` and were unaffected, which is why this survived three releases: only a project driven by `mcpp test` hits it. The symptom lands three levels from the cause — a consumer failing to link with `libX11.so: undefined reference to xcb_connect` (alongside `libxcb.so.1 ... not found`), or a test binary exiting 127. mcpp-index CI has been failing this way on gui-stack, imgui-module and imgui-window since 0.0.104; two probe PRs pinning only MCPP_VERSION over unmodified descriptors reproduced it at both 0.0.104 and 0.0.106, which is what ruled out the package-identity migration as the cause. Hang the alias off the consumer's implicit inputs, beside the .so it already lists. Correct under `default` and under explicit goals alike, and it pulls in nothing that was not already being built. e2e 64 covered only `build` + `run` — precisely the two paths that still worked. It now also runs `mcpp test` from a clean target dir and asserts the alias exists; without the fix that test binary fails with exit 127. Verified: unit 37/37; e2e 64 red before / green after; the three real mcpp-index members pass with `mcpp test` alone (gui-stack 5/5, imgui-module 1/1, imgui-window 1/1). Remaining local e2e failures (22, 98, 141) reproduce identically on the released 0.0.106 binary under the same MCPP_HOME — they are this machine's gcc 15.1.0, not this change.
Sunrisepeak
added a commit
that referenced
this pull request
Jul 25, 2026
… line (0.0.108) (#285) `mcpp test` names every shared prerequisite as a ninja goal so a broken package source fails once, as a package error, instead of N times as identical per-test compile failures. For a large package that is thousands of object paths: FFmpeg's 2281 translation units produced a 50,781-character argv. Windows joins argv into a single command string for cmd.exe, which caps at 8191 characters, so the command never ran at all — the 127 came back from cmd.exe, before ninja or mcpp could print anything. That silence is what made it hard to place. mcpp-index's Windows job has failed on the ffmpeg member since 0.0.104, and the log's last line was an unrelated download progress bar: no "build failed" diagnostic, no ninja output, and target/.build_cache never written. ffmpeg is the only member large enough to trip the limit, and `mcpp build` / `mcpp run` drive `default` with no goal arguments, so both stayed green throughout. Emit the goal set as a phony edge in build.ninja and pass its one-word name. The manifest has no length limit, and ninja still builds the whole set in a single invocation, so parallelism is unchanged. Same origin as the soname-alias regression fixed in 0.0.107: both come from the explicit-goal-targets change in #274 — one design change, two symptoms that only appear under conditions the test suite did not cover. e2e 164 asserts the mechanism (goals live in the manifest) rather than the 8191 limit: reproducing the limit needs a package far too slow to build here, and the limit does not exist on Linux or macOS. It is red on 0.0.107 and green here. Verified: unit 37/37; e2e 155 passed / 1 failed / 5 skipped, the one failure (22_doctor_cache_publish) reproducing identically on the released binary under the same MCPP_HOME. Found by publishing an instrumented Windows build to a throwaway prerelease and pinning it from a stripped-down mcpp-index probe PR — four rounds of black-box probing could not see inside the process.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
mcpp test 能力批次 — 0.0.104
mcpp test从「单次构建 + 顺序运行」升级为练习级/CI 级可用的测试运行器。两轮批次合并交付,设计评审与路线图见.agents/docs/2026-07-24-mcpp-test-design-review.md,实施计划见.agents/docs/2026-07-23-test-isolation-json-plan.md与2026-07-24-test-batch2-plan.md。新增
tests/00-a/0.cpp→00-a/0,子目录布局可用mcpp test <pattern>:按名字子串过滤(只作用于构建/运行,compile_commands 保持完整)mcpp test --list:枚举测试不构建;JSON 记录供工具消费mcpp test --timeout <secs>:每测试运行截止(POSIX)--message-format json:逐测试 NDJSON(status/exit_code/signal/duration_ms/timed_out/compile_output/run_output)+ 包级错误记录 + summary[build].flagsglob 覆盖测试 TU;死 glob 警告改为查磁盘BuildOptions::ninjaTargets/keepGoing:后端 goal 子集构建的通用接口修复
WIFSIGNALED → 128+WTERMSIG(此前 SIGTERM 死亡伪装成 exit 15)LD_LIBRARY_PATH段错误根治:merged_environ剥离私有 glibc loader 条目(下游 d2x/d2mcpp 的 unsetenv workaround 可删)Compiling → 结果 → 诊断连续块,删除误导性中场 Finished 横幅/的命名豁免验证