31000dcbe3
tracker-policy-pr / check-pr (pull_request) Successful in 12s
test / integration-docker (pull_request) Successful in 15s
test / unit (pull_request) Successful in 39s
test / stage-firecracker-inputs (pull_request) Successful in 1s
lint / lint (push) Failing after 2m36s
test / build-infra (pull_request) Successful in 4m13s
test / integration-firecracker (pull_request) Successful in 1m30s
test / coverage (pull_request) Successful in 2m12s
test / publish-infra (pull_request) Has been skipped
If resolve_teardown_timeout() raised after launch_consolidated()/register_agent() returned, the teardown callback was never registered, leaving the bottle registered with no cleanup path. Resolve the timeout into a local variable before the registration call so any failure aborts before the bottle exists. Add tests covering OrchestratorConfigStore, resolve_teardown_timeout priority ordering (env > db > default), and the source-order invariant that the resolver runs before registration in all three backends.