fix(ci): restore unit_tests dependency on coverage job (PR #10845 v2)
CI / benchmark-publish (pull_request) Has been skipped
CI / benchmark-regression (pull_request) Failing after 56s
CI / build (pull_request) Successful in 1m1s
CI / helm (pull_request) Successful in 35s
CI / lint (pull_request) Successful in 1m16s
CI / quality (pull_request) Successful in 1m15s
CI / typecheck (pull_request) Successful in 1m39s
CI / security (pull_request) Successful in 1m50s
CI / push-validation (pull_request) Successful in 25s
CI / integration_tests (pull_request) Successful in 3m31s
CI / e2e_tests (pull_request) Successful in 4m19s
CI / unit_tests (pull_request) Failing after 4m46s
CI / coverage (pull_request) Has been skipped
CI / docker (pull_request) Has been skipped
CI / status-check (pull_request) Failing after 3s

Per review feedback from HAL9001, the coverage job must depend on unit_tests
passing to prevent misleading coverage reports when tests fail. Without this
dependency, coverage could run and report false-positive pass results even
when unit tests are failing — undermining the purpose of the quality gate.

Additionally: commit footer ISSUES CLOSED: #1641 included in parent commit.

ISSUES CLOSED: #10845
This commit is contained in:
2026-05-11 01:46:17 +00:00
parent c82dabaf7b
commit d1d492d859
+3 -4
View File
@@ -395,10 +395,9 @@ jobs:
container:
image: ${{vars.docker_prefix}}python:3.13-slim
# Coverage runs the full unit-test suite independently under slipcover.
# It no longer waits for lint/typecheck/security/quality -- those jobs
# are independent static-analysis checks that do not affect test results.
# Removing the unnecessary dependency allows coverage to start immediately
# in parallel with all other jobs, cutting the critical path significantly.
# It depends on unit_tests so coverage results are only meaningful when
# tests actually pass — prevents misleading coverage reports when tests fail.
needs: [unit_tests]
steps:
- name: Install system dependencies (nodejs for checkout, git for merge tests)
run: |