Add regression test proving Req 4.4/7.2: a second WAL_CONFIG_MARKER committing while the first's forced checkpoint is still in flight (simulated via the checkpoint_in_progress CAS across both markers' commit+apply) cleanly supersedes it, with the settled state reflecting only the newer marker. Verified via a field-aware byte comparison (post-checkpoint_lsn) against a non-racing control fixture, plus mid-race assertions that materialization is still incomplete at that point (cfgref_present false, fence set) despite activation already tracking the newer config. Test-only; production mechanism (already implemented) unmodified. Suite: 1027 -> 1028 tests, 0 failures. |
||
|---|---|---|
| .. | ||
| settings | ||
| specs | ||
| steering | ||