test: isolate CLI output capture with monkeypatch/redirect to fix stdout corruption in full suite (Issue #178) #180
No Reviewers
Labels
Clear labels
allocator
anti-stomp
architecture
bug
chore
codex
concurrency
contamination
control-plane
dashboard
database
design
documentation
enhancement
gitea
glitchtip
important
incident
incident-bridge
integration
jenkins
labels
leases
mcp
mcp-health
mcp-menu
multi-project
mutating
nice-to-have
observability
portability
preflight
protected-branch
queue
read-only
reconnect
recovery
refactor
release
reliability
resumable-review
reviewer
roadmap
safety
security
self-hosted
sentry
stale-runtime
status:blocked
status:in-progress
status:pr-open
status:ready
terminal-lock
testing
tracker
type:bug
type:feature
type:feature
type:guardrail
visibility
workflow
workflow-hardening
workflow-hardening
Controller-owned work allocator
Prevent concurrent LLM session stomping
Architecture / structural design
OpenAI Codex client / workflow session surface
Concurrent session safety
Workflow or session contamination incident
MCP control-plane coordination and allocation authority
MCP operational dashboard/queue view
Internal coordination storage (SQLite/Postgres)
Design / investigation, no implementation
Docs / runbooks
New feature or improvement
Gitea MCP workflow
GlitchTip integration
Operational or process incident requiring durable audit trail
Sentry-to-Gitea incident bridging
Integration testing
Jenkins integration
Label taxonomy management
Lease adopt/release/expire lifecycle
MCP server / tooling
MCP namespace and runtime health
MCP menu surface
Work spanning multiple monitoring projects or Gitea repos
Mutating action; requires gating
Observability, metrics, traces, error reporting
Cross-platform / portability
Shared preflight gates before mutation
Protected branch / stable-branch policy concern
Work queue visibility and allocation
Read-only, no mutation
MCP client reconnect/reload recovery path
Recovery paths for stale/foreign leases
Code refactor / restructure
Release / versioning
Reliability / failure handling
Persist and resume prepared review verdicts across sessions
Reviewer workflow tooling
Roadmap / umbrella issue
Safety rails and fail-closed mutation guards
Security / trust boundary
Self-hosted infrastructure integration
Sentry error monitoring integration
Stale backend daemon / runtime-vs-master parity failures
Issue is blocked
Issue is being worked on
Issue has an open pull request
Issue is ready for work
Terminal review lock (#332) path
Tests / test coverage
Issue tracker hygiene / meta
Bug or defect
Feature or enhancement
Feature or enhancement
Safety gate or guardrail
Workflow state visibility for LLMs/operators
Cross-tool workflow
LLM workflow coordination hardening
LLM workflow coordination hardening
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Scaled-Tech-Consulting/Gitea-Tools#180
Reference in New Issue
Block a user
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.
Fixes the test suite stdout capture issue (discovered during #176 validation) that forced junitxml workaround.
This improves reliability for blind PR queue review validation (related to #173).
Refs #178
Co-Authored-By: Claude Opus 4.8 (1M context) [email protected]
- Replace raw patch("sys.stdout") and contextlib.redirect_stderr with pytest MonkeyPatch or contextlib redirect scoped to main calls in CLI tests (create_*, prs, python_cli, manage_labels, merge_pr, review_pr). - Add regression tests in test_review_proofs.py for stdout/stderr remaining usable. - Ensures normal pytest summary output without junitxml workaround; improves review validation reporting per #173. - No behavior change to production code or gates. Refs #178Review requirement (from operator triage of the authoring Grok run — tracked in #183):
Before approving or merging this PR, the reviewer must verify, at the pinned head (
ff4ab500df8447f4409b3e9cc262520e8076d806at the time of this note; re-pin if it moves):./venv/bin/python -m pytest tests/ --ignore=branchesand confirm it prints a normal pytest summary line to the terminal without any junitxml workaround. The author report cited targeted tests and subprocess pipe capture but did not show this canonical run's visible summary — that is the acceptance criterion of #178, so the review must produce it.Refs #178, a non-closing keyword — Gitea will not auto-close #178 on merge. Either the PR body should be corrected toCloses #178/Fixes #178, or the merger must close #178 manually (and removestatus:in-progress) after verifying the fix.Author-run reporting gaps observed in the same run (missing Controller Handoff, unknown-capability claim proof for
gitea_mark_issue, inexact sweep evidence, missing head SHA) are consolidated in #183 and do not block this PR on their own.I have checked out head SHA
ff4ab500df, verified it matches local HEAD, and reviewed the diff against master. The changes isolate stdout/stderr redirects in the CLI test modules (e.g., using pytest's MonkeyPatch or contextlib.redirect_stdout), resolving the stdout pollution and corruption issue. Standard and full test suites run successfully and print normal summary output without swallowing stdout. Targeted tests pass cleanly (37 passed). Full test suite passes cleanly (677 passed, 6 skipped).