Live deploy journal now honors test-only fault injection, and health-check failure rolls back to the previous release.
make test-lifecycle runs the real combination suite when PostgreSQL, RDM source, and both binaries are present, and fails closed when any of them is missing.
Login stays NOT_RUN because the RDM binary has no account CLI. Full-track deploy stays on the svc-realcombo job.
GATE: current HEAD CI jobs test, test-pg (make test-lifecycle), and svc-realcombo
## Summary
- Live deploy journal now honors test-only fault injection, and health-check failure rolls back to the previous release.
- `make test-lifecycle` runs the real combination suite when PostgreSQL, RDM source, and both binaries are present, and fails closed when any of them is missing.
- Login stays NOT_RUN because the RDM binary has no account CLI. Full-track deploy stays on the svc-realcombo job.
## Test plan
- [x] SELF: `python3 -m unittest tests.test_svc_u2.U2ReleaseTests -q` (35 ok, 1 skipped)
- [ ] GATE: current HEAD CI jobs test, test-pg (`make test-lifecycle`), and svc-realcombo
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-svc-d3-lifecycle-gate.md; R0=5212fef01e59b7f9e12fa7fc42cd987c6792a786.
Impact: task metadata only; the feature workspace starts at 5212fef01e.
Refs: .task/feature-svc-d3-lifecycle-gate.md
Why: The live deploy journal never called fault injection, and test-lifecycle failed closed on login so CI could not require the real combination cases.
Evidence: SELF python3 -m unittest tests.test_svc_u2.U2ReleaseTests -q exit 0 (35 ok, 1 skipped) on 3602a87; receipt sha256 9b5785577751e8e9e7947cf9700fb8854b1c80142f34273ae25f3097ee4c9aa8.
Impact: test-pg builds the Dev binary and runs make test-lifecycle. Login and full-track deploy without SVC_RDM_ORIGIN stay NOT_RUN. No live data move and no account CLI.
Refs: recovery plan D2/D3; Dev #485
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The task card needs the pull request link and the decision not to move live instance data before review.
Evidence: SELF python3 /tmp/d1d3-ro-instances.py exit 0; receipt sha256 895676aabddf85c5b36966428204fde160846b70ac5a8b5eb90ab8037bb0897a. An earlier evidence attempt failed on a broken checker and is kept.
Impact: No runtime data was moved. Login and authenticated rdm.ping stay NOT_RUN.
Refs: Dev #495
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The release tests must be bound to the commit that contains the lifecycle changes, and the pre-merge sync has to be on the card.
Evidence: SELF make task-sync exit 0, receipt sha256 ef762f87ad785ef9a1759e2686a992353161e35c7a80b726e01133f1779329af. SELF python3 -m unittest tests.test_svc_u2.U2ReleaseTests -q exit 0 on 0dce930 (35 ok, 1 skipped), receipt sha256 cfe7aea9e6bb09f7a169a4caab3c1c89b4b3138c4e08fa11f53bf12d13caa46a.
Impact: Task metadata only. origin/main 5212fef was already contained.
Refs: Dev #495
Co-authored-by: Cursor <cursoragent@cursor.com>
weichen
merged commit 6ecf903757 into main2026-10-13 01:29:06 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
make test-lifecycleruns the real combination suite when PostgreSQL, RDM source, and both binaries are present, and fails closed when any of them is missing.Test plan
python3 -m unittest tests.test_svc_u2.U2ReleaseTests -q(35 ok, 1 skipped)make test-lifecycle), and svc-realcombo