test: make test_health portable for scratch clones (closes #245) #248
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#248
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.
Description
Fix
tests/test_health.pyso reviewer scratch-clone validation no longer requires a repo-localvenv/bin/python.Changes
_health_test_python(): prefersys.executable, thenGITEA_TOOLS_TEST_PYTHON, elseSkipTest_run_python_script(): subprocess timeout + terminate/kill teardownValidation
Closes #245
Review summary
Reviewed PR #248 at head
d422bc0978de30fff70e7eeaad5f3de48b260097.Scope: Matches #245 — makes
tests/test_health.pyportable for reviewer scratch clones by preferringsys.executableover a hard-codedvenv/bin/python, withGITEA_TOOLS_TEST_PYTHONoverride andSkipTestfallback. Adds subprocess timeout/teardown in_run_python_script(). Documents scratch-clone norm inreview-pr.mdtemplate.Findings:
_run_python_script()is a solid improvement over baresubprocess.run.tests/test_health.py; skip message still says "repo venv not available" though venv is no longer required.Validation (reviewer worktree, pinned head):
pytest tests/test_health.py -q→ 5 passedpytest tests/ -q→ full suite passed (exit 0)git diff --check master...HEAD→ cleanVerdict: Approve. Ready to merge into
master.Reconciliation review (sysadmin)
Re-checked PR #248 at pinned head
d422bc0978de30fff70e7eeaad5f3de48b260097.Prior approval attempt left a PENDING draft (Gitea event mismatch: MCP sends
APPROVE, Gitea expectsAPPROVEDper #244). This resubmit attempts visible approval reconciliation.Validation:
pytest tests/test_health.py -v→ 5 passed;git diff --check→ clean.Scope: 2 files (
tests/test_health.py,review-pr.mdtemplate) — matches #245.APPROVE — PR #248
Validated against pinned head
d422bc0978de30fff70e7eeaad5f3de48b260097.Scope: Clean — 2 files (
tests/test_health.py,skills/llm-project-workflow/templates/review-pr.md), matches #245. UsesCloses #245.Changes: Portable interpreter resolution (
sys.executable→GITEA_TOOLS_TEST_PYTHON→ SkipTest); subprocess timeout/teardown helpers; two new unit tests; review-pr template note for scratch-clone validation.Validation:
unittest tests.test_health -v— 5/5 passed (from/tmpclone path; see note below)Note:
test_startup_conflict_detectionfails when cwd path containsbranches/(review worktree location) becausemcp_server.check_conflict_markers()skips any tree whose path containsbranches. Pre-existing; passes from main repo or/tmpclone. Not introduced by this PR.Worktree:
branches/review-feat-issue-245-test-health-portable(detached, clean)Review Metadata: