Order reservation conflict check before refusal
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / checks (postgres) (push) Successful in 47m55s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 5s
Foundation / postgres-tools (push) Successful in 20s

This commit is contained in:
dingo
2026-10-10 19:35:45 -04:00
parent ecbad78267
commit 4c4ab367f4
2 changed files with 10 additions and 1 deletions
+6
View File
@@ -5733,3 +5733,9 @@ durable `existing_life` refusal and allocates its own identity. Updated the chec
to assert the returned identity and rejection value, and aligned the reservation
contract text with v17. PostgreSQL is unavailable in this Windows environment;
the focused and full database checks await CI.
The next run failed that assertion because the new request was first issued only
after the original reservation had been refused. Moved the first conflicting
request before that refusal, then kept the later call as an exact-retry check.
The latest SQL adjustment has not yet run in CI; PostgreSQL remains unavailable
locally.