You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The runtime audit harness (#6903) passed while #6906s real-codebase regression (test files wrongly scanned + CoreBoundaryLeak explosion) slipped through, because the fixture had no tests/ subdir (walker test-path skip never exercised) and no forbidden-ecosystem-term content (agnostic detector never triggered). Adds: a tests/-subdir fixture file containing a forbidden term that MUST be skipped (snapshot asserts its absence; a #6906-style regression makes it appear and fails the harness), a behavioral forbidden-term file that fires, and an explicit test-path-invariant test. Fixtures + test only; no detector/config change. This is the prerequisite for safely landing #6855 Phase 1.
ℹ️ No tests ran — the runner failed before producing results. See raw_output.stderr_tail / raw_output.stdout_tail for the underlying error (bootstrap failure, missing deps, DB connection, etc.).
ℹ️ To run specific tests: homeboy test homeboy -- --filter=TestName
ℹ️ Auto-fix lint issues: homeboy refactor homeboy --from lint --write
ℹ️ Collect coverage: homeboy test homeboy --coverage
ℹ️ Analyze failures: homeboy test homeboy --analyze
ℹ️ Pass args to test runner: homeboy test -- [args]
ℹ️ Full options: homeboy docs commands/test
Deep dive: homeboy test homeboy --changed-since 2ef1265
Artifacts and drill-down
CI results artifact: homeboy-ci-results-homeboy-test-homeboy-Linux contains immediate command JSON for this action invocation.
Observation artifact: homeboy-observations-homeboy-test-homeboy-Linux contains exported Homeboy run history for deeper queries.
Drill-down: download the observation artifact, then run homeboy runs import <dir>, homeboy runs list, and homeboy runs findings <run-id>.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The runtime audit harness (#6903) passed while #6906s real-codebase regression (test files wrongly scanned + CoreBoundaryLeak explosion) slipped through, because the fixture had no tests/ subdir (walker test-path skip never exercised) and no forbidden-ecosystem-term content (agnostic detector never triggered). Adds: a tests/-subdir fixture file containing a forbidden term that MUST be skipped (snapshot asserts its absence; a #6906-style regression makes it appear and fails the harness), a behavioral forbidden-term file that fires, and an explicit test-path-invariant test. Fixtures + test only; no detector/config change. This is the prerequisite for safely landing #6855 Phase 1.