mirror of
https://github.com/brazilofmux/tinymux
synced 2026-08-13 00:23:11 -04:00
8ab84b6064
Lenovo found while reviewing this PR that tests/libmux rebuilds only on test_libmux.cpp, so editing a header it compiles against rebuilds nothing and the suite reports green against the previous header. That disarms precisely the negative control this PR adds: regress alloc.h, re-run without a clean, and the safe_chr test passes because it is still the old object. My own verification happened to run `make -C tests/libmux clean` first, so the result stood -- but only by habit, and the guard would have been inert for anyone who did the natural thing afterwards. -MMD -MP emits header prerequisites beside the object, and the generated .d is -included and cleaned. Verified in Lenovo's exact scenario: from a green tree, regress alloc.h, no clean -- the object now rebuilds and the watchdog fires with its named message, then restores to green. Fixes only this harness. #1952 covers the remaining nine, which is the better-shaped change; this one is taken here because it is this PR's test that the gap disarms, and shipping a guard that cannot fire is the exact failure this suite keeps finding elsewhere. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| Makefile | ||
| test_libmux.cpp | ||