Bind durable mutation reservations to cellular ticks
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 1m56s
Foundation / checks (checks) (push) Failing after 3m58s
Foundation / checks (tsan) (push) Canceled after 0s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (client) (push) Canceled after 6m18s
Foundation / checks (postgres) (push) Canceled after 2m23s
Foundation / checks (network) (push) Canceled after 4m19s

This commit is contained in:
dingo
2026-10-11 08:54:50 -04:00
parent b0cd2b7704
commit de4bbec94c
5 changed files with 206 additions and 20 deletions
+9 -9
View File
@@ -6870,12 +6870,12 @@ not visible from this workspace, so its current value is unverified.
Run #280 (commit `bfa0e1d`) exercised the workflow after adding a Harbor-gate
diagnostic. Its network suite failed at `tests/network_control.cpp:375`: the
negative test still treats protocol version 10 as a future unsupported version,
although M11.4c now defines the v10 mutation-action codec. The failed checks
matrix blocked `server-image` and `image`, so this run did not attempt either an
image build or Harbor publication. The narrow proposed test correction is to
use version 11 for the future-version case; the test file remains untouched
pending resolution of its earlier review restriction. The local focused Windows
build for the next M11.4c reservation-to-tick adapter also stalled without
output and was stopped; `git diff --check` passed, but the adapter remains
unvalidated until CI can run it.
negative test still treated protocol version 10 as a future unsupported
version, although M11.4c defines the v10 mutation-action codec. The failed
checks matrix blocked `server-image` and `image`, so that run attempted neither
an image build nor Harbor publication. The future-version test now uses v11;
the M11.4c reservation-to-tick adapter is included in the next CI run so the
network, native, server-image and Harbor gates can all be evaluated together.
The local focused Windows build stalled without output and was stopped;
`git diff --check` passed, but CI must validate the adapter. Harbor's repository
setting remains unverified until that run reaches and reports the publish gate.