Format PostgreSQL parser return
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 1m57s
Foundation / checks (client) (push) Successful in 15m14s
Foundation / checks (network) (push) Successful in 15m15s
Foundation / checks (tsan) (push) Successful in 8m43s
Foundation / checks (checks) (push) Successful in 36m44s
Foundation / checks (postgres) (push) Failing after 23m32s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 1m57s
Foundation / checks (client) (push) Successful in 15m14s
Foundation / checks (network) (push) Successful in 15m15s
Foundation / checks (tsan) (push) Successful in 8m43s
Foundation / checks (checks) (push) Successful in 36m44s
Foundation / checks (postgres) (push) Failing after 23m32s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped
This commit is contained in:
@@ -6935,3 +6935,8 @@ The affected action-record, migration-record, commit-status, publication-action,
|
||||
and life-owner parsers now use safe optional defaults or checked copies; missing
|
||||
mutation input retains its prior absent-value behavior. The PostgreSQL job failed
|
||||
on these analyzer diagnostics, so the dependent image jobs did not start.
|
||||
Run #293's main checks job stopped at format-check before compilation because the
|
||||
new optional-return expression wrapped at line 499. It has been kept on one
|
||||
line to follow the 100-column clang-format configuration. PostgreSQL analysis
|
||||
continued independently, but was superseded before completion by the format fix
|
||||
push so the full matrix could rerun on one commit.
|
||||
|
||||
Reference in New Issue
Block a user