chore(ORCH-111): retrigger merge-gate re-test (flaked under host CPU starvation)

Browse Source

The merge-gate re-test bounced ORCH-111 to development with 1 failed + 40
errors in 488s — a resource-exhaustion signature, NOT a code defect:

- This branch is watchdog-only (watchdog/** + compose); it touches no src/,
  no STAGE_TRANSITIONS/QG_CHECKS/check_*, and no tests/test_stage_engine.py.
- The failing tests (test_stage_engine.py::TestStagingInfraTolerance
  tc02/tc12/tc13/tc14) are outside this branch's scope, pass in isolation
  (5 passed/19s), and pass right after the new watchdog tests (105 passed).
  tc14 takes NO fixtures yet "errored" — a systemic/host failure, not logic.
- Host load was ~10-12 on a 4-core box at re-test time (the exact orphaned-
  pytest CPU-starvation incident ORCH-111 alerts on; ORCH-111 by design only
  observes, it does not reap — BR-3).

Evidence the branch is sound: full `pytest tests/` is green locally
(1933 passed, 0 failed, 0 errors in 267s, well under the 600s budget) and
Gitea CI on the branch HEAD is green (push + pull_request). Empty commit to
re-run the pipeline now that host load has dropped (10.5 -> 6).

Refs: ORCH-111
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

...

This commit is contained in:

claude-bot

2026-06-15 02:39:59 +03:00

parent 1fbfb941a9

commit 4311720c39

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

Diff Content Not Available