From d5b342a1ac785811f9a2939afb01678d46705327 Mon Sep 17 00:00:00 2001 From: Feanil Patel Date: Tue, 16 Jun 2026 11:28:36 -0400 Subject: [PATCH] build: suppress per-shard pytest coverage table in unit-tests CI Each unit-test shard was printing a ~3,700-line per-file coverage table at the end of its log (the default `--cov=.` behavior is `--cov-report=term`). The numbers are also misleading per shard because each shard only runs a subset of the suite. The dedicated `coverage` job already does the meaningful work: it downloads every shard's `.coverage` artifact, runs `coverage combine` + `coverage report` + `coverage xml`, and uploads the result to codecov. Passing `--cov-report=""` to pytest disables the terminal report while leaving the `.coverage` data file intact, so codecov reporting is unaffected and the failure summary is much easier to find in the CI log. Co-authored-by: Claude Opus 4.7 (1M context) --- .github/workflows/unit-tests.yml | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/.github/workflows/unit-tests.yml b/.github/workflows/unit-tests.yml index 777af3491eb6..a70bdd00acd6 100644 --- a/.github/workflows/unit-tests.yml +++ b/.github/workflows/unit-tests.yml @@ -121,8 +121,12 @@ jobs: - name: run tests shell: bash run: | - python -Wd -m pytest -p no:randomly --ds=${{ env.settings_path }} ${{ env.unit_test_paths }} --cov=. \ - ${{ env.report_log_arg }} + # --cov-report="" suppresses the per-shard terminal coverage table + # (~3.7k lines of noise). The .coverage data file is still written and + # uploaded as an artifact for the combined `coverage` job below, which + # is what reports to codecov. + python -Wd -m pytest -p no:randomly --ds=${{ env.settings_path }} ${{ env.unit_test_paths }} \ + --cov=. --cov-report="" ${{ env.report_log_arg }} - name: Upload pytest timing report if: github.ref == 'refs/heads/master'