Repository navigation
🐛🧑💻 - Review claims a unittest module never runs despite wildcard discovery and actual CI execution #806
Description
Is there an existing issue for this?
- I have searched the existing issues for unittest/wildcard/test-discovery false positives. No matching report was found. 🐛🧑💻 - Bugbot reconciliation retains an orphan unknown finding alongside duplicate semantic reports #655 covers separate reconciliation/semantic-duplicate observations; 🐛🧑💻 - Bugbot confuses generated Kotlin source lines and flags correct JaCoCo missed line assertions #796 covers a different compiled-line attribution false positive.
Which actions are affected?
Pull Request
Which platforms are affected?
Linux self-hosted Action; independent discovery control on macOS.
Description
Bugbot reports that test_wire_export_task.py is never run by CI, despite the configured runner selecting test_wire_*.py and actual CI executing all five methods from that exact module. Its suggestion would add a redundant invocation to an already wired suite.
The precise internal cause (context selection, glob interpretation or analysis reasoning) is not established. This is a grounded review-quality counterexample, not a request to ignore genuine missing-test wiring or relax review gates.
Reproducing the issue
Observed GeckoCV source: 1b5e3a0ade73d21c749bceba004230fc97f2713e, PR vypdev/geckocv#42.
- Original native finding: https://github.com/vypdev/geckocv/pull/42#discussion_r4423890193
- Review workflow: https://github.com/vypdev/geckocv/actions/runs/41059078157
- Actual backend producer: https://github.com/vypdev/geckocv/actions/runs/41059078060
- The backend workflow invokes
.github/scripts/tests/run_wire_transport_tests.py. - That runner calls subprocess unittest discovery with the arguments below; it does not select only test_wire_transport.py.
[sys.executable, "-m", "unittest", "discover", "-s", ".github/scripts/tests",
"-p", "test_wire_*.py", "-v"]Independent unittest.defaultTestLoader.discover('.github/scripts/tests', pattern='test_wire_*.py') lists 19 cases, including all five test_wire_export_task.WireExportTaskTests cases. This control performs discovery only; it is not counted as another test execution.
The actual completed native producer log separately records all five as ... ok:
test_a_passing_test_without_export_is_still_a_failed_producer
test_main_export_cannot_reuse_previous_serializer_fixture_evidence
test_missing_exporter_fails_and_removes_old_evidence_even_with_no_test_sources
test_output_symlink_does_not_change_its_target
test_parent_symlink_is_rejected_before_any_write
Ran 19 tests in 50.251s
The five names belong to the disputed module and are a subset of 19, not 24 distinct cases. Source and CI invocation remain unchanged; this report does not fabricate execution by adding an invocation after the finding.
copilot Version
Observed review uses published vypdev/copilot@v3 at f5e5a4c / 3.10.6. No claim is made about an unexecuted newer release or an internal root cause.
Relevant Log Output
The finding says: "the wire transport runner runs its own named test module" and that "no workflow invokes this file directly". The configured wildcard and actual five module-qualified OK records above contradict the claimed missing execution. This is separate from whether a file is invoked directly rather than included through discovery.
Additional context and comments
Please cover wildcard-based Python discovery and indirect runner delegation in source-grounding/evaluation, including genuinely excluded-module negative controls, and consult available same-source execution evidence before asserting a test is never run. Preserve conservative handling of missing or ambiguous evidence.
Please handle the correction through the Copilot team's normal workflow. This reporter has not started an upstream implementation branch, changed correct consumer discovery, reduced scope, lowered thresholds or published a release/deployment. Other real GeckoCV review defects remain open.
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
[-]Review claims a unittest module never runs despite wildcard discovery and actual CI execution[/-][+]🐛 - Review claims a unittest module never runs despite wildcard discovery and actual CI execution[/+]vypbot commentedon Oct 30, 2026
Hi! I’m @vypbot, the Copilot assistant for this repository.
I can answer questions, explain the codebase, propose implementation and test plans, review issues and pull requests for potential bugs or security problems, and help authorized maintainers apply changes.
Try
/copilot helpto see the available commands, or mention @vypbot with your question.[-]🐛 - Review claims a unittest module never runs despite wildcard discovery and actual CI execution[/-][+]🐛🧑💻 - Review claims a unittest module never runs despite wildcard discovery and actual CI execution[/+]vypbot commentedon Oct 30, 2026
Implementation plan
Acceptance: The new discovery cases pass the existing Bugbot evaluation thresholds, the included excluded-module controls retain their expected findings, and documentation makes clear that evaluation fixtures do not prove general model accuracy.
Need something else? Mention the bot with a question or use
/copilot help.vypbot commentedon Oct 30, 2026
Issue closed — historical progress
Current status: closed as completed.
The last estimate is retained below as history. Closure does not certify a new percentage, tests, or branch alignment.
Action required: none for this closed issue. If work continues, reopen the issue; a fresh assessment can update this same card.
Last assessment before closure (historical)
vypbot commentedon Oct 30, 2026
Issue closed: synchronization recommendation retired
No branch synchronization is required for this closed issue.
The previous recommendation is historical. Issue closure does not certify that the branches are synchronized.