Audit cellular profile migration grants
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 6s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (ecs) (push) Successful in 1m54s
Foundation / checks (tsan) (push) Successful in 8m45s
Foundation / checks (postgres) (push) Failing after 32m38s
Foundation / checks (checks) (push) Successful in 37m25s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 6s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (ecs) (push) Successful in 1m54s
Foundation / checks (tsan) (push) Successful in 8m45s
Foundation / checks (postgres) (push) Failing after 32m38s
Foundation / checks (checks) (push) Successful in 37m25s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped
This commit is contained in:
@@ -7024,3 +7024,5 @@ CI run #310 passed client, deploy, ECS and network. The main checks stopped at t
|
||||
CI run #311 passed client, deploy, ECS, network and TSan, and compiled the PostgreSQL test target. The PostgreSQL analysis build then still reported 17 unchecked accesses: clang-tidy does not treat the `CHECK(...)` macro or `optional::value()` by itself as proof of engagement. The test now uses a helper with an explicit `has_value()` guard before dereferencing those optionals. This version awaits CI validation; PostgreSQL tools and Harbor publication did not start.
|
||||
|
||||
CI run #312 passed client, deploy, ECS and network, but the PostgreSQL-enabled test build found that the new `checked_value` helper only accepted `std::optional`, while the SHA-256 helper returns `std::expected`. The test now provides the same explicit engagement check for `std::expected`; run #312 did not reach PostgreSQL tools or server-image/Harbor publication.
|
||||
|
||||
CI run #313 passed client, deploy, ECS, network and TSan; both PostgreSQL compilation configurations completed. The PostgreSQL integration run then failed its final runtime-role audit because the cellular profile-migration publisher and lookup are explicitly granted to the runtime role but were missing from the audit's fenced-function set. Those two lease-fenced functions are now listed, and the online migration test now expects the current schema version 29 after upgrading its v7 fixture. PostgreSQL tools and Harbor publication did not start.
|
||||
|
||||
Reference in New Issue
Block a user