Fix lineage mutation test constness
Foundation / checks (client) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (ecs) (push) Successful in 1m56s
Foundation / checks (checks) (push) Failing after 4m0s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (postgres) (push) Canceled after 8m38s
Foundation / checks (tsan) (push) Canceled after 6m48s

This commit is contained in:
dingo
2026-10-11 06:46:34 -04:00
parent 9156e1cc0b
commit 8336cb41aa
2 changed files with 8 additions and 1 deletions
+7
View File
@@ -6785,3 +6785,10 @@ test completed: both targeted Ninja invocations stalled without output and were
stopped. The C++ and SQL publishers deliberately refuse batches containing
mutation selections until durable action reservation, publication and recovery
are implemented. Formatting and Linux CI remain pending for this segment.
Run 265 compiled the M11.4c owner and trace code, then stopped in
`tests/lineage_tests.cpp`: a decoded archive was held through a const expected
before a negative death-mutation assertion. The fixture now keeps that decoded
archive mutable. Local clang-format and `git diff --check` passed; the targeted
Windows lineage-test build again produced no output for 60 seconds and was
stopped. Full CI follow-up is pending.
+1 -1
View File
@@ -408,7 +408,7 @@ void genome_revisions_preserve_birth_and_replay_current_genome() {
CHECK(archive.current_genome(50) && *archive.current_genome(50) == 11);
CHECK(!archive.record_mutation(50, descend(12, 11), evo::Tick{103}));
const auto died_bytes = archive.encode();
const auto died = LineageArchive::decode(died_bytes);
auto died = LineageArchive::decode(died_bytes);
CHECK(died && died->current_genome(50) && *died->current_genome(50) == 11);
CHECK(!died->record_death(50, evo::Tick{101}));
}