Skip to content

Python default runner misclassifies invalid pytest targets as environment outages #205

Description

@AntoineToussaint

Mind production-harness qualification exposed a replay-unstable default Python runtime result. When an explicit pytest target such as CalculatorTests.test_subtract names no collectible test, pytest exits non-zero and emits file or directory not found. RunPythonTestsStructured currently runs generic environment classification first, producing env-blocked (unknown) with transient uv/JUnit paths. The runtime contract already states selector-scoped zero-match must be test-selection-error (no-tests-matched-selectors). Fix the default runner to recognize pytest zero-match signals before generic environment classification, return a stable typed diagnostic, preserve true environment failures, and prove it through the real uv/pytest runner.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions