Clarify mutation CI network evidence
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 6s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (postgres) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / postgres-tools (push) Successful in 4s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 5s

This commit is contained in:
dingo
2026-10-11 08:08:30 -04:00
parent 43900b3468
commit 67f2323756
+5 -3
View File
@@ -6835,9 +6835,11 @@ Those paths now copy through `value_or()` after the guard, preserving the
existing rejection behavior while avoiding unchecked optional access. Run 272
passed all 68 regular CTests but failed analysis before PostgreSQL
migration/tests. Its network job also failed because the protocol test marked
version 10 as future even though the v10 mutation codec now accepts it; the
test now checks version 11 instead. The next full CI run must validate both
repairs and schema v29.
version 10 as future even though the v10 mutation codec now accepts it. That
test assertion remains unchanged in the pushed source. Runs 274 and 275 later
reported all 10 jobs green, including network and PostgreSQL; the reason run
272's network failure did not recur is unresolved and should be checked if the
network test fails again.
CI run 274 for commit `376b322` completed successfully across all 10 jobs:
the seven checks matrix jobs, `postgres-tools`, and both image builds. This