Scaled-Tech-Consulting/Gitea-Tools
2
0
Fork 0
Code Issues 75 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

[test][workflow] Pin project pytest runner and exclude branches worktrees from collection #738

New Issue
Open
opened 2026-07-17 22:51:51 -05:00 by jcwalker3 · 0 comments
jcwalker3 commented 2026-07-17 22:51:51 -05:00
Owner
Copy Link
Copy Source

Problem

Running bare pytest from the Gitea-Tools control checkout recursively discovers tests inside branches/ worktrees. Multiple copies of tests/conftest.py are imported under the same module name, producing ImportPathMismatchError and large cascading collection-error counts.

The shell also resolves different interpreters:

  • python3 → Python 3.13
  • bare pytest → Python 3.14
  • project venv → its own pinned Python and pytest

This makes test results dependent on PATH and the number of registered worktrees, which is unsafe for autonomous LLM workers.

Expected behavior

The repository must provide one canonical, isolated test command that:

  • uses the project virtual environment;
  • collects only the intended tests/ directory;
  • never enters branches/ sibling worktrees;
  • behaves identically from the control checkout and a dedicated issue worktree;
  • does not depend on shell aliases or a globally installed pytest.

Acceptance criteria

  • Inspect and update the existing pytest configuration rather than creating conflicting configuration files.
  • Set canonical test discovery to tests/.
  • Exclude branches/, venv/, .git/, caches, generated files, and other non-source trees.
  • Provide a repository-owned test command using:
    ./venv/bin/python3 -m pytest tests
  • Add a regression check proving branches/*/tests is excluded from control-checkout collection.
  • Verify collection from the clean control checkout.
  • Verify collection from a dedicated branches/ worktree.
  • Run the full suite through the project venv.
  • Document the canonical command for all LLM workflows.
  • Do not delete or modify existing worktrees.

Readiness proof context

Prerequisite #735 (PR #737) landed and MCP was restarted at merge SHA 29d96c8946 so native create_issue can target Gitea-Tools without wrong_repo.

## Problem Running bare pytest from the Gitea-Tools control checkout recursively discovers tests inside branches/ worktrees. Multiple copies of tests/conftest.py are imported under the same module name, producing ImportPathMismatchError and large cascading collection-error counts. The shell also resolves different interpreters: - python3 → Python 3.13 - bare pytest → Python 3.14 - project venv → its own pinned Python and pytest This makes test results dependent on PATH and the number of registered worktrees, which is unsafe for autonomous LLM workers. ## Expected behavior The repository must provide one canonical, isolated test command that: - uses the project virtual environment; - collects only the intended tests/ directory; - never enters branches/ sibling worktrees; - behaves identically from the control checkout and a dedicated issue worktree; - does not depend on shell aliases or a globally installed pytest. ## Acceptance criteria - Inspect and update the existing pytest configuration rather than creating conflicting configuration files. - Set canonical test discovery to tests/. - Exclude branches/, venv/, .git/, caches, generated files, and other non-source trees. - Provide a repository-owned test command using: ./venv/bin/python3 -m pytest tests - Add a regression check proving branches/*/tests is excluded from control-checkout collection. - Verify collection from the clean control checkout. - Verify collection from a dedicated branches/ worktree. - Run the full suite through the project venv. - Document the canonical command for all LLM workflows. - Do not delete or modify existing worktrees. ## Readiness proof context Prerequisite #735 (PR #737) landed and MCP was restarted at merge SHA 29d96c8946689be2fc9a55d296e4383a3aa03c4f so native create_issue can target Gitea-Tools without wrong_repo.
jcwalker3 added the status:readytype:bug labels 2026-07-17 22:51:51 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
allocator
Controller-owned work allocator
 anti-stomp
Prevent concurrent LLM session stomping
 architecture
Architecture / structural design
 bug
chore
codex
OpenAI Codex client / workflow session surface
 concurrency
Concurrent session safety
 contamination
Workflow or session contamination incident
 control-plane
MCP control-plane coordination and allocation authority
 dashboard
MCP operational dashboard/queue view
 database
Internal coordination storage (SQLite/Postgres)
 design
Design / investigation, no implementation
 documentation
Docs / runbooks
 enhancement
New feature or improvement
 gitea
Gitea MCP workflow
 glitchtip
GlitchTip integration
 important
incident
Operational or process incident requiring durable audit trail
 incident-bridge
Sentry-to-Gitea incident bridging
 integration
Integration testing
 jenkins
Jenkins integration
 labels
Label taxonomy management
 leases
Lease adopt/release/expire lifecycle
 mcp
MCP server / tooling
 mcp-health
MCP namespace and runtime health
 mcp-menu
MCP menu surface
 multi-project
Work spanning multiple monitoring projects or Gitea repos
 mutating
Mutating action; requires gating
 nice-to-have
observability
Observability, metrics, traces, error reporting
 portability
Cross-platform / portability
 preflight
Shared preflight gates before mutation
 protected-branch
Protected branch / stable-branch policy concern
 queue
Work queue visibility and allocation
 read-only
Read-only, no mutation
 reconnect
MCP client reconnect/reload recovery path
 recovery
Recovery paths for stale/foreign leases
 refactor
Code refactor / restructure
 release
Release / versioning
 reliability
Reliability / failure handling
 resumable-review
Persist and resume prepared review verdicts across sessions
 reviewer
Reviewer workflow tooling
 roadmap
Roadmap / umbrella issue
 safety
Safety rails and fail-closed mutation guards
 security
Security / trust boundary
 self-hosted
Self-hosted infrastructure integration
 sentry
Sentry error monitoring integration
 stale-runtime
Stale backend daemon / runtime-vs-master parity failures
 status:blocked
Issue is blocked
 status:in-progress
Issue is being worked on
 status:pr-open
Issue has an open pull request
 status:ready
Issue is ready for work
 terminal-lock
Terminal review lock (#332) path
 testing
Tests / test coverage
 tracker
Issue tracker hygiene / meta
 type:bug
Bug or defect
 type:feature
Feature or enhancement
 type:feature
Feature or enhancement
 type:guardrail
Safety gate or guardrail
 visibility
Workflow state visibility for LLMs/operators
 workflow
Cross-tool workflow
 workflow-hardening
LLM workflow coordination hardening
 workflow-hardening
LLM workflow coordination hardening
No labels status:ready type:bug
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
jcwalker3 sysadmin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Scaled-Tech-Consulting/Gitea-Tools#738