Record blocked server image run
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 4s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 4s
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:52:10 -04:00
parent bfa0e1d637
commit b0cd2b7704
+12
View File
@@ -6867,3 +6867,15 @@ skipped the server-image build. This explains why those green runs produced no
new image. Harbor publication has a separate gate: the main-branch job pushes
only when `HARBOR_SERVER_REPOSITORY` is configured. That repository variable is
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.