Files
orchestrator/tests
claude-bot 26d6f31c05
All checks were successful
CI / test (push) Successful in 1m12s
CI / test (pull_request) Successful in 1m16s
fix(tests): make test_orch123 R-2 hermetic vs merged ORCH-123 staging log (ORCH-119)
test_r2_held_deploy_staging_not_rolled_back reused its own (now-merged)
work-item id ORCH-123. With the default repos_dir=/repos, the staging gate's
origin/main fallback (check_staging_status -> _staging_log_from_main) found
ORCH-123's REAL staging_status: SUCCESS log in origin/main and flipped the
deliberately-red gate green, firing advance_stage. The flake surfaced only in
the full suite (the repos_dir singleton is fixed by the first config-importing
file, defeating this module's import-time ORCH_REPOS_DIR=/tmp).

Pin repos_dir to an isolated empty tmp dir in the autouse fresh_db fixture
(mirroring the already-pinned worktrees_dir) so the gate has no real clone to
read -> genuinely red -> the ORCH-123 R-2 invariant (infra-held deploy-staging
is HELD, never rolled back to development) stays verifiable, order-independent.
Test-only; no product code / gate semantics touched. Full suite: 2173 passed.

Refs: ORCH-119

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-17 14:46:15 +03:00
..