fix(ci): add unit_tests to coverage job needs to prevent misleading parallel results #10884

Merged
HAL9000 merged 1 commits from fix/ci-coverage-job-ordering into master 2026-04-28 11:50:18 +00:00

1 Commits

Author SHA1 Message Date
HAL9000 bfbe9b27d3 fix(ci): add unit_tests to coverage job needs to prevent misleading parallel results
CI / benchmark-publish (pull_request) Has been skipped
CI / helm (pull_request) Successful in 28s
CI / lint (pull_request) Successful in 1m5s
CI / push-validation (pull_request) Successful in 39s
CI / build (pull_request) Successful in 48s
CI / quality (pull_request) Successful in 1m39s
CI / typecheck (pull_request) Successful in 1m59s
CI / security (pull_request) Successful in 1m58s
CI / integration_tests (pull_request) Successful in 4m9s
CI / e2e_tests (pull_request) Successful in 4m41s
CI / unit_tests (pull_request) Successful in 5m15s
CI / docker (pull_request) Successful in 1m31s
CI / coverage (pull_request) Successful in 11m17s
CI / status-check (pull_request) Successful in 7s
The coverage job in ci.yml previously only depended on [lint, typecheck,
security, quality], allowing it to run in parallel with unit_tests. This
meant coverage could report a pass even when unit tests were still running
or had already failed, wasting CI resources and producing misleading results.

Adding unit_tests to the coverage job's needs list ensures coverage only
starts after tests have passed, eliminating the redundant parallel test
execution and making coverage results meaningful.

ISSUES CLOSED: #10714
2026-04-28 11:30:13 +00:00