TEST-INFRA: [ci-execution-time] Slow e2e tests #1748

New issue

Open

opened 2026-04-02 23:41:12 +00:00 by freemo · 1 comment

freemo commented

2026-04-02 23:41:12 +00:00

Owner

Metadata

Branch: test/ci-execution-time-slow-e2e-tests
Commit Message: test(ci): reduce e2e test suite execution time
Milestone: v3.2.0
Parent Epic: #1678

Description

The e2e_tests suite is taking a long time to run, significantly slowing down the CI/CD pipeline. On average, this suite takes over 15 minutes to complete.

Analysis

Average Execution Time: 15 minutes (900 seconds)
Impact: This is the second longest running check in the CI pipeline, and it is a major bottleneck for pull request validation.

Recommendations

Parallelize test execution: The end-to-end tests should be parallelized to run on multiple runners simultaneously. This could significantly reduce the overall execution time.
Optimize test setup and teardown: Analyze the test setup and teardown procedures to identify any unnecessary or time-consuming operations.
Identify and optimize slow tests: Profile the end-to-end tests to identify individual tests that are taking a long time to run and optimize them.
Split the test suite: If parallelization is not enough, consider splitting the end-to-end test suite into smaller, more manageable chunks that can be run independently.

Subtasks

Investigate the feasibility of parallelizing the end-to-end tests.
Profile the end-to-end tests to identify slow tests.
Create a plan for optimizing the test setup and teardown.
Implement the chosen optimization strategy.

Definition of Done

The execution time of the e2e_tests suite is reduced by at least 50%.
The CI/CD pipeline is significantly faster.
The changes are documented and communicated to the team.
All nox stages pass.
Coverage >= 97%.

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

## Metadata - **Branch**: `test/ci-execution-time-slow-e2e-tests` - **Commit Message**: `test(ci): reduce e2e test suite execution time` - **Milestone**: v3.2.0 - **Parent Epic**: #1678 ## Description The `e2e_tests` suite is taking a long time to run, significantly slowing down the CI/CD pipeline. On average, this suite takes over 15 minutes to complete. ## Analysis - **Average Execution Time:** 15 minutes (900 seconds) - **Impact:** This is the second longest running check in the CI pipeline, and it is a major bottleneck for pull request validation. ## Recommendations - **Parallelize test execution:** The end-to-end tests should be parallelized to run on multiple runners simultaneously. This could significantly reduce the overall execution time. - **Optimize test setup and teardown:** Analyze the test setup and teardown procedures to identify any unnecessary or time-consuming operations. - **Identify and optimize slow tests:** Profile the end-to-end tests to identify individual tests that are taking a long time to run and optimize them. - **Split the test suite:** If parallelization is not enough, consider splitting the end-to-end test suite into smaller, more manageable chunks that can be run independently. ## Subtasks - [ ] Investigate the feasibility of parallelizing the end-to-end tests. - [ ] Profile the end-to-end tests to identify slow tests. - [ ] Create a plan for optimizing the test setup and teardown. - [ ] Implement the chosen optimization strategy. ## Definition of Done - [ ] The execution time of the `e2e_tests` suite is reduced by at least 50%. - [ ] The CI/CD pipeline is significantly faster. - [ ] The changes are documented and communicated to the team. - [ ] 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-02 23:41:56 +00:00

freemo added a new dependency

2026-04-02 23:48:18 +00:00

#1678 Epic: CI Execution Time Optimization — Timeouts, Concurrency, and Coverage Artifact Sharing

freemo commented

2026-04-02 23:51:01 +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 added the

MoSCoW

Could have

label

2026-04-02 23:51:01 +00:00