[AUTO-INF-5] CI: Coverage job has incorrect dependencies and is not using test results #8079

Open
opened 2026-04-13 03:26:47 +00:00 by HAL9000 · 0 comments
Owner

Metadata

  • Commit message: ci: fix coverage job dependencies to include unit_tests and integration_tests
  • Branch name: ci/fix-coverage-job-dependencies

Background and Context

The coverage job in the CI pipeline (.forgejo/workflows/ci.yml) is configured to run after lint, typecheck, security, and quality jobs, but it does not depend on unit_tests or integration_tests.

This means the coverage report is generated without waiting for the tests that produce the coverage data. The job is likely reporting on stale or non-existent coverage information, making the coverage metric unreliable and potentially misleading. CI coverage gates based on this job cannot be trusted.

Expected Behavior

The coverage job in .forgejo/workflows/ci.yml declares unit_tests and integration_tests in its needs list, ensuring the coverage report is always generated using the results of the most recent test runs:

coverage:
  runs-on: docker
  container:
    image: python:3.13-slim
  needs: [lint, typecheck, security, quality, unit_tests, integration_tests]

The coverage metric is accurate and reflects actual test execution results.

Acceptance Criteria

  • The coverage job in .forgejo/workflows/ci.yml includes unit_tests and integration_tests in its needs list.
  • The coverage job runs only after both unit_tests and integration_tests have completed successfully.
  • The coverage report reflects the output of the most recent test runs, not stale or missing data.
  • All existing CI jobs continue to pass after the change.
  • No regressions are introduced in any test suite or build artifact.

Subtasks

  • Inspect .forgejo/workflows/ci.yml to confirm the current needs list for the coverage job.
  • Add unit_tests and integration_tests to the needs list of the coverage job.
  • Verify the updated pipeline runs correctly end-to-end (coverage job waits for test jobs).
  • Confirm the coverage report reflects actual test results after the fix.
  • Open a PR with the change and link it to this issue.

Definition of Done

This issue should be closed when:

  • The coverage job's needs list includes both unit_tests and integration_tests.
  • The CI pipeline runs successfully end-to-end with no regressions.
  • The coverage report is confirmed to reflect actual test execution results.
  • All acceptance criteria above are verified and checked off.

Duplicate Check

  • Searched open issues for "coverage dependency": 0 results
  • Searched closed issues for "coverage dependency": 0 results
  • Searched open issues for "coverage report": 0 results relevant to dependencies
  • Searched closed issues for "coverage report": 0 results relevant to dependencies
  • Searched open issues for "test data": 0 results relevant to coverage job

This issue was automatically generated by the test-infra-pool-supervisor with session tag [AUTO-INF-5].


Automated by CleverAgents Bot
Agent: new-issue-creator

## Metadata - **Commit message:** `ci: fix coverage job dependencies to include unit_tests and integration_tests` - **Branch name:** `ci/fix-coverage-job-dependencies` ## Background and Context The `coverage` job in the CI pipeline (`.forgejo/workflows/ci.yml`) is configured to run after `lint`, `typecheck`, `security`, and `quality` jobs, but it does **not** depend on `unit_tests` or `integration_tests`. This means the coverage report is generated without waiting for the tests that produce the coverage data. The job is likely reporting on stale or non-existent coverage information, making the coverage metric unreliable and potentially misleading. CI coverage gates based on this job cannot be trusted. ## Expected Behavior The `coverage` job in `.forgejo/workflows/ci.yml` declares `unit_tests` and `integration_tests` in its `needs` list, ensuring the coverage report is always generated using the results of the most recent test runs: ```yaml coverage: runs-on: docker container: image: python:3.13-slim needs: [lint, typecheck, security, quality, unit_tests, integration_tests] ``` The coverage metric is accurate and reflects actual test execution results. ## Acceptance Criteria - [ ] The `coverage` job in `.forgejo/workflows/ci.yml` includes `unit_tests` and `integration_tests` in its `needs` list. - [ ] The `coverage` job runs only after both `unit_tests` and `integration_tests` have completed successfully. - [ ] The coverage report reflects the output of the most recent test runs, not stale or missing data. - [ ] All existing CI jobs continue to pass after the change. - [ ] No regressions are introduced in any test suite or build artifact. ## Subtasks - [ ] Inspect `.forgejo/workflows/ci.yml` to confirm the current `needs` list for the `coverage` job. - [ ] Add `unit_tests` and `integration_tests` to the `needs` list of the `coverage` job. - [ ] Verify the updated pipeline runs correctly end-to-end (coverage job waits for test jobs). - [ ] Confirm the coverage report reflects actual test results after the fix. - [ ] Open a PR with the change and link it to this issue. ## Definition of Done This issue should be closed when: - The `coverage` job's `needs` list includes both `unit_tests` and `integration_tests`. - The CI pipeline runs successfully end-to-end with no regressions. - The coverage report is confirmed to reflect actual test execution results. - All acceptance criteria above are verified and checked off. --- ### Duplicate Check - Searched open issues for "coverage dependency": 0 results - Searched closed issues for "coverage dependency": 0 results - Searched open issues for "coverage report": 0 results relevant to dependencies - Searched closed issues for "coverage report": 0 results relevant to dependencies - Searched open issues for "test data": 0 results relevant to coverage job --- *This issue was automatically generated by the `test-infra-pool-supervisor` with session tag `[AUTO-INF-5]`.* --- **Automated by CleverAgents Bot** Agent: new-issue-creator
HAL9000 added this to the v3.5.0 milestone 2026-04-13 03:27:31 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
cleveragents/cleveragents-core#8079
No description provided.