TEST-INFRA: [ci-execution-time] Investigate and optimize the e2e_tests job #1912

Open
opened 2026-04-03 00:11:55 +00:00 by freemo · 2 comments
Owner

Metadata

  • Branch: task/ci-investigate-optimize-e2e-tests-job
  • Commit Message: perf(ci): investigate and optimize e2e_tests job to reduce execution time
  • Milestone: v3.2.0
  • Parent Epic: #1678

Summary

The e2e_tests CI job is consistently one of the longest-running jobs in the CI pipeline. On average, it takes over 10 minutes to complete. This significantly slows down the feedback loop for developers and increases the overall CI execution time.

Subtasks

  • Analyze the e2e_tests job to identify the bottlenecks.
  • Investigate opportunities for optimization, such as:
    • Caching dependencies.
    • Parallelizing tasks.
    • Optimizing the test setup and teardown.
  • Implement the identified optimizations.
  • Run nox (all default sessions), fix any errors.
  • Verify coverage >=97% via nox -s coverage_report.

Definition of Done

  • The execution time of the e2e_tests job is reduced by at least 50%.
  • The changes are deployed to the CI pipeline.
  • A Git commit is created where the first line of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation.
  • The commit is pushed to the remote on the branch matching the Branch in Metadata exactly.
  • The commit is submitted as a pull request to master, reviewed, and merged before this issue is marked done.
  • All nox stages pass.
  • Coverage >= 97%.

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

## Metadata - **Branch**: `task/ci-investigate-optimize-e2e-tests-job` - **Commit Message**: `perf(ci): investigate and optimize e2e_tests job to reduce execution time` - **Milestone**: v3.2.0 - **Parent Epic**: #1678 ## Summary The `e2e_tests` CI job is consistently one of the longest-running jobs in the CI pipeline. On average, it takes over 10 minutes to complete. This significantly slows down the feedback loop for developers and increases the overall CI execution time. ## Subtasks - [ ] Analyze the `e2e_tests` job to identify the bottlenecks. - [ ] Investigate opportunities for optimization, such as: - Caching dependencies. - Parallelizing tasks. - Optimizing the test setup and teardown. - [ ] Implement the identified optimizations. - [ ] Run `nox` (all default sessions), fix any errors. - [ ] Verify coverage >=97% via `nox -s coverage_report`. ## Definition of Done - [ ] The execution time of the `e2e_tests` job is reduced by at least 50%. - [ ] The changes are deployed to the CI pipeline. - [ ] A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation. - [ ] The commit is pushed to the remote on the branch matching the **Branch** in Metadata exactly. - [ ] The commit is submitted as a **pull request** to `master`, reviewed, and **merged** before this issue is marked done. - [ ] All nox stages pass. - [ ] Coverage >= 97%. --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: ca-new-issue-creator
freemo added this to the v3.2.0 milestone 2026-04-03 00:12:11 +00:00
Author
Owner

Issue triaged by project owner:

  • State: Verified
  • MoSCoW: MoSCoW/Could Have — CI/test infrastructure improvement.

Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: ca-project-owner

Issue triaged by project owner: - **State**: Verified - **MoSCoW**: MoSCoW/Could Have — CI/test infrastructure improvement. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner
freemo removed this from the v3.2.0 milestone 2026-04-06 22:31:28 +00:00
Author
Owner

This issue has been moved to the backlog as part of an aggressive grooming of the v3.2.0 milestone. It has been deemed non-critical for the minimal viability of the milestone and will be addressed in a future release.

This issue has been moved to the backlog as part of an aggressive grooming of the v3.2.0 milestone. It has been deemed non-critical for the minimal viability of the milestone and will be addressed in a future release.
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#1912
No description provided.