TEST-INFRA: [ci-execution-time] Optimize and fix coverage report generation #6094

Open
opened 2026-04-09 14:32:04 +00:00 by HAL9000 · 0 comments
Owner

Metadata

  • Branch: test-infra/optimize-coverage-report-generation
  • Commit Message: perf(ci): optimize and fix coverage report generation to prevent timeouts
  • Milestone: (backlog — see note below)
  • Parent Epic: #5924

Summary

The nox -e coverage_report session is consistently timing out in CI. This prevents the project from tracking its test coverage and ensuring that new code is adequately tested.

Problem

The coverage report generation times out because it depends on the unit_tests and integration_tests sessions, which are also timing out. Even if the test sessions were to complete, the coverage report generation itself might be slow.

Proposed Solution

  1. Fix Test Timeouts: The coverage_report timeout is a symptom of the test timeouts. The issues for parallelizing the test suites must be addressed first.
  2. Optimize Coverage Report Generation: Investigate ways to speed up the coverage report generation. This could include:
    • Excluding irrelevant files and directories from the coverage report.
    • Using a faster coverage tool or configuration.
    • Running the coverage report generation on a more powerful runner.
  3. Adjust CI Workflow: Ensure that the coverage_report session is only run after the unit_tests and integration_tests sessions have completed successfully. The total execution time of all three sessions should be within the CI timeout.

Subtasks

  • Ensure that the issues for parallelizing the unit_tests and integration_tests suites are resolved.
  • Analyze the coverage.xml generation process to identify bottlenecks.
  • Optimize the coverage report configuration to exclude unnecessary files.
  • Update the CI workflow to ensure the correct execution order and to prevent timeouts.

Definition of Done

  • The coverage_report session completes successfully in CI without timing out.
  • The project's test coverage is successfully reported in every CI run.
  • All nox stages pass.
  • Coverage >= 97%.

Duplicate Check

  • Search queries: coverage report timeout, optimize coverage, coverage_report slow
  • Results: No existing issues found that address the optimization of the coverage report generation.

Backlog note: This issue was discovered during autonomous operation
on milestone v3.8.0. It does not block milestone completion and has been
placed in the backlog for human review and future milestone assignment.


Automated by CleverAgents Bot
Supervisor: Test Infrastructure | Agent: new-issue-creator

## Metadata - **Branch**: `test-infra/optimize-coverage-report-generation` - **Commit Message**: `perf(ci): optimize and fix coverage report generation to prevent timeouts` - **Milestone**: *(backlog — see note below)* - **Parent Epic**: #5924 ## Summary The `nox -e coverage_report` session is consistently timing out in CI. This prevents the project from tracking its test coverage and ensuring that new code is adequately tested. ## Problem The coverage report generation times out because it depends on the `unit_tests` and `integration_tests` sessions, which are also timing out. Even if the test sessions were to complete, the coverage report generation itself might be slow. ## Proposed Solution 1. **Fix Test Timeouts:** The `coverage_report` timeout is a symptom of the test timeouts. The issues for parallelizing the test suites must be addressed first. 2. **Optimize Coverage Report Generation:** Investigate ways to speed up the coverage report generation. This could include: * Excluding irrelevant files and directories from the coverage report. * Using a faster coverage tool or configuration. * Running the coverage report generation on a more powerful runner. 3. **Adjust CI Workflow:** Ensure that the `coverage_report` session is only run after the `unit_tests` and `integration_tests` sessions have completed successfully. The total execution time of all three sessions should be within the CI timeout. ## Subtasks - [ ] Ensure that the issues for parallelizing the `unit_tests` and `integration_tests` suites are resolved. - [ ] Analyze the `coverage.xml` generation process to identify bottlenecks. - [ ] Optimize the coverage report configuration to exclude unnecessary files. - [ ] Update the CI workflow to ensure the correct execution order and to prevent timeouts. ## Definition of Done - [ ] The `coverage_report` session completes successfully in CI without timing out. - [ ] The project's test coverage is successfully reported in every CI run. - [ ] All nox stages pass. - [ ] Coverage >= 97%. ### Duplicate Check - Search queries: `coverage report timeout`, `optimize coverage`, `coverage_report slow` - Results: No existing issues found that address the optimization of the coverage report generation. > **Backlog note:** This issue was discovered during autonomous operation > on milestone v3.8.0. It does not block milestone completion and has been > placed in the backlog for human review and future milestone assignment. --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: new-issue-creator
HAL9000 added this to the v3.8.0 milestone 2026-04-09 21:19:18 +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.

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