Skip to content

fix: pass BASE_TEST_ENV to the coverage target - #1183

Open
vladch-outreach wants to merge 1 commit into
mainfrom
fix/coverage-test-tags
Open

fix: pass BASE_TEST_ENV to the coverage target#1183
vladch-outreach wants to merge 1 commit into
mainfrom
fix/coverage-test-tags

Conversation

@vladch-outreach

@vladch-outreach vladch-outreach commented Aug 18, 2026

Copy link
Copy Markdown
  • coverage hand-rolled its environment with only GOPROXY/GOPRIVATE, so TEST_TAGS never reached test.sh, which defaults it to empty.
  • make coverage therefore ran untagged while test and test-e2e did not, dropping any package whose tests reach an or_test-gated dependency out of the coverage run.
  • docs/makefile.md already documents the default as or_test.

Why: searchproxy/internal/searchproxy/server_test.go excludes itself from coverage builds and cites this gap by name.

The coverage target hand-rolled its environment with only GOPROXY and
GOPRIVATE, so TEST_TAGS was never exported. shell/test.sh defaults it to
empty, meaning make coverage ran untagged while make test and test-e2e
did not.

Untagged builds exclude or_test-gated files, so any package whose tests
reach a tagged dependency fails to compile and is dropped from the
coverage run, under-reporting coverage for every Go service.
@vladch-outreach
vladch-outreach requested a review from a team as a code owner August 18, 2026 18:07
@getoutreach-ci-2

Copy link
Copy Markdown

Link to code coverage report (posted by coverbot 🤖)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant