Mark/mesh-seed

Fork 0

INFRA-015: Fix test collection errors blocking full suite #112

New issue

Closed

opened 2026-04-10 01:02:00 +00:00 by Mark · 1 comment

Mark commented

2026-04-10 01:02:00 +00:00

Owner

Problem

6 test files fail during collection with import/dependency errors, preventing the full test suite (1763 tests) from running.

Errors

ERROR tests/load/test_auto_scaling.py
ERROR tests/load/test_queue_depth.py
ERROR tests/production/test_e2e_production.py
ERROR tests/production/test_real_ollama.py
ERROR tests/test_deployment_worker.py
ERROR tests/unit/test_capability_execution.py

Impact

1763 tests collected, 6 errors - Cannot run full suite
Unknown test coverage - Do not know what is broken
CI/CD unreliable - Cannot trust test results
Regression risk - Changes may break untested code paths

Scope (MINIMAL)

Run each error file individually to identify specific import errors
Fix import paths and missing dependencies
Mock external services if needed
Document environment requirements

Files

tests/load/test_auto_scaling.py
tests/load/test_queue_depth.py
tests/production/test_e2e_production.py
tests/production/test_real_ollama.py
tests/test_deployment_worker.py
tests/unit/test_capability_execution.py

Acceptance Criteria

All 6 test files collect without errors
Full test suite runs (1763 tests)
Import errors resolved
CI can run complete test suite

May be related to Issue #111 (meta_factory loading)
Related to Issue #100 (E2E test infrastructure)

## Problem 6 test files fail during collection with import/dependency errors, preventing the full test suite (1763 tests) from running. ## Errors ``` ERROR tests/load/test_auto_scaling.py ERROR tests/load/test_queue_depth.py ERROR tests/production/test_e2e_production.py ERROR tests/production/test_real_ollama.py ERROR tests/test_deployment_worker.py ERROR tests/unit/test_capability_execution.py ``` ## Impact - 1763 tests collected, 6 errors - Cannot run full suite - Unknown test coverage - Do not know what is broken - CI/CD unreliable - Cannot trust test results - Regression risk - Changes may break untested code paths ## Scope (MINIMAL) 1. Run each error file individually to identify specific import errors 2. Fix import paths and missing dependencies 3. Mock external services if needed 4. Document environment requirements ## Files - tests/load/test_auto_scaling.py - tests/load/test_queue_depth.py - tests/production/test_e2e_production.py - tests/production/test_real_ollama.py - tests/test_deployment_worker.py - tests/unit/test_capability_execution.py ## Acceptance Criteria - [ ] All 6 test files collect without errors - [ ] Full test suite runs (1763 tests) - [ ] Import errors resolved - [ ] CI can run complete test suite ## Related - May be related to Issue #111 (meta_factory loading) - Related to Issue #100 (E2E test infrastructure)

Mark referenced this issue

2026-04-10 01:02:41 +00:00

INFRA-001: Restore infrastructure proxy bidding subscription in mesh_node.py #98

Mark referenced this issue

2026-04-10 01:07:09 +00:00

INFRA-003: Create true E2E test for full intent execution flow #100

Mark added the

feature-request

label

2026-05-12 23:53:05 +00:00

Mark added

blocked:needs-decision

and removed

feature-request

labels

2026-05-18 05:00:57 +00:00

Mark commented

2026-05-18 05:00:57 +00:00

Author

Owner

Feature Triage Assessment

Scope: small
Risk: low
Spec Alignment: misaligned
Summary: Issue #112 proposes fixing collection errors in 6 test files, but those files were already deleted in commit ee5b7db as part of purging 64 fake tests that 'gave false confidence' — the problem no longer exists.
Recommendation: Close as obsolete. The 6 files listed (tests/load/test_auto_scaling.py, tests/load/test_queue_depth.py, tests/production/test_e2e_production.py, tests/production/test_real_ollama.py, tests/test_deployment_worker.py, tests/unit/test_capability_execution.py) were removed in the April 10 architecture fix. The current 367-test suite collects cleanly (verified). If coverage is needed in these areas, file NEW issues scoped to specific, currently-missing test categories with a clear target module to test.
Rationale: SCOPE=small: The proposed fix is for 6 files, but they no longer exist. RISK=low: No code changes needed — the problem is already resolved. SPEC=misaligned: The issue's premise ('6 test files fail during collection, 1763 tests total') contradicts the current codebase state where those files don't exist and only 367 tests collect successfully. The issue body and acceptance criteria reference a version of the codebase that no longer exists — implementing it would mean resurrecting the fake tests that were intentionally deleted.

Labeled blocked:needs-decision — unblock on Forgejo to dispatch to the fixer pipeline.

## Feature Triage Assessment **Scope:** small **Risk:** low **Spec Alignment:** misaligned **Summary:** Issue #112 proposes fixing collection errors in 6 test files, but those files were already deleted in commit ee5b7db as part of purging 64 fake tests that 'gave false confidence' — the problem no longer exists. **Recommendation:** Close as obsolete. The 6 files listed (tests/load/test_auto_scaling.py, tests/load/test_queue_depth.py, tests/production/test_e2e_production.py, tests/production/test_real_ollama.py, tests/test_deployment_worker.py, tests/unit/test_capability_execution.py) were removed in the April 10 architecture fix. The current 367-test suite collects cleanly (verified). If coverage is needed in these areas, file NEW issues scoped to specific, currently-missing test categories with a clear target module to test. **Rationale:** SCOPE=small: The proposed fix is for 6 files, but they no longer exist. RISK=low: No code changes needed — the problem is already resolved. SPEC=misaligned: The issue's premise ('6 test files fail during collection, 1763 tests total') contradicts the current codebase state where those files don't exist and only 367 tests collect successfully. The issue body and acceptance criteria reference a version of the codebase that no longer exists — implementing it would mean resurrecting the fake tests that were intentionally deleted. Labeled `blocked:needs-decision` — unblock on Forgejo to dispatch to the fixer pipeline.

Mark removed the

blocked:needs-decision

label

2026-05-28 07:19:13 +00:00

Mark added the

triage-approved

bug

quickfix

labels

2026-06-07 05:48:10 +00:00

Mark

2026-06-16 09:24:20 +00:00