fix(ci): add unit_tests to coverage job needs to prevent misleading parallel results
CI / benchmark-publish (pull_request) Has been skipped
CI / push-validation (pull_request) Successful in 34s
CI / helm (pull_request) Successful in 41s
CI / build (pull_request) Successful in 52s
CI / lint (pull_request) Successful in 1m9s
CI / quality (pull_request) Successful in 1m21s
CI / typecheck (pull_request) Successful in 1m39s
CI / security (pull_request) Successful in 1m40s
CI / e2e_tests (pull_request) Successful in 4m17s
CI / integration_tests (pull_request) Successful in 5m23s
CI / unit_tests (pull_request) Successful in 6m15s
CI / docker (pull_request) Successful in 1m28s
CI / coverage (pull_request) Successful in 11m0s
CI / status-check (pull_request) Successful in 3s
CI / benchmark-publish (pull_request) Has been skipped
CI / push-validation (pull_request) Successful in 34s
CI / helm (pull_request) Successful in 41s
CI / build (pull_request) Successful in 52s
CI / lint (pull_request) Successful in 1m9s
CI / quality (pull_request) Successful in 1m21s
CI / typecheck (pull_request) Successful in 1m39s
CI / security (pull_request) Successful in 1m40s
CI / e2e_tests (pull_request) Successful in 4m17s
CI / integration_tests (pull_request) Successful in 5m23s
CI / unit_tests (pull_request) Successful in 6m15s
CI / docker (pull_request) Successful in 1m28s
CI / coverage (pull_request) Successful in 11m0s
CI / status-check (pull_request) Successful in 3s
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
This commit is contained in: