TEST-INFRA: [ci-execution-time] Parallelize test execution to reduce CI pipeline time #2279

Closed
opened 2026-04-03 12:47:19 +00:00 by freemo · 1 comment
Owner

Metadata

  • Branch: chore/ci-parallelize-test-execution
  • Commit Message: chore(ci): parallelize unit, integration, and e2e test jobs to reduce pipeline time
  • Milestone: v3.8.0
  • Parent Epic: #1678

Background and Context

The CI pipeline currently runs the unit_tests, integration_tests, and e2e_tests jobs sequentially. This leads to a longer overall pipeline duration than necessary, as these jobs are independent and could be run in parallel.

Analysis

The CI configuration file (.forgejo/workflows/ci.yml) shows that the test jobs are defined as separate, independent jobs with no explicit dependencies between them that would require sequential execution. The final status-check job depends on all of them, but they do not depend on each other.

Expected Behavior

The unit_tests, integration_tests, and e2e_tests jobs should execute in parallel, reducing overall CI wall-clock time without affecting correctness or the status-check aggregation step.

Acceptance Criteria

  • The unit_tests, integration_tests, and e2e_tests jobs run in parallel in the CI pipeline.
  • The status-check job correctly gathers results from all parallel jobs.
  • The overall CI pipeline execution time is measurably reduced.

Subtasks

  • Audit .forgejo/workflows/ci.yml to confirm no hidden sequential dependencies between unit_tests, integration_tests, and e2e_tests
  • Modify the CI configuration to run the unit_tests, integration_tests, and e2e_tests jobs in parallel by removing any implicit sequential ordering
  • Ensure the status-check job correctly gathers results from all parallel jobs
  • Update features/ci_workflow_validation.feature to assert parallel execution of the three test jobs
  • Run nox (all default sessions), fix any errors
  • Verify coverage >= 97% via nox -s coverage_report

Definition of Done

  • All subtasks above are completed and checked off.
  • The unit_tests, integration_tests, and e2e_tests jobs run in parallel in the CI pipeline.
  • The status-check job correctly gathers the results from all parallel jobs.
  • The overall CI pipeline execution time is reduced.
  • 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**: `chore/ci-parallelize-test-execution` - **Commit Message**: `chore(ci): parallelize unit, integration, and e2e test jobs to reduce pipeline time` - **Milestone**: v3.8.0 - **Parent Epic**: #1678 ## Background and Context The CI pipeline currently runs the `unit_tests`, `integration_tests`, and `e2e_tests` jobs sequentially. This leads to a longer overall pipeline duration than necessary, as these jobs are independent and could be run in parallel. ## Analysis The CI configuration file (`.forgejo/workflows/ci.yml`) shows that the test jobs are defined as separate, independent jobs with no explicit dependencies between them that would require sequential execution. The final `status-check` job depends on all of them, but they do not depend on each other. ## Expected Behavior The `unit_tests`, `integration_tests`, and `e2e_tests` jobs should execute in parallel, reducing overall CI wall-clock time without affecting correctness or the `status-check` aggregation step. ## Acceptance Criteria - The `unit_tests`, `integration_tests`, and `e2e_tests` jobs run in parallel in the CI pipeline. - The `status-check` job correctly gathers results from all parallel jobs. - The overall CI pipeline execution time is measurably reduced. ## Subtasks - [ ] Audit `.forgejo/workflows/ci.yml` to confirm no hidden sequential dependencies between `unit_tests`, `integration_tests`, and `e2e_tests` - [ ] Modify the CI configuration to run the `unit_tests`, `integration_tests`, and `e2e_tests` jobs in parallel by removing any implicit sequential ordering - [ ] Ensure the `status-check` job correctly gathers results from all parallel jobs - [ ] Update `features/ci_workflow_validation.feature` to assert parallel execution of the three test jobs - [ ] Run `nox` (all default sessions), fix any errors - [ ] Verify coverage >= 97% via `nox -s coverage_report` ## Definition of Done - [ ] All subtasks above are completed and checked off. - [ ] The `unit_tests`, `integration_tests`, and `e2e_tests` jobs run in parallel in the CI pipeline. - [ ] The `status-check` job correctly gathers the results from all parallel jobs. - [ ] The overall CI pipeline execution time is reduced. - [ ] 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.8.0 milestone 2026-04-03 12:47:41 +00:00
Author
Owner

Closing as duplicate of #2293.

This issue ("Parallelize test execution to reduce CI pipeline time") covers the same scope as #2293 ("Parallelize Nox Sessions in CI") — both aim to run independent test jobs in parallel in the CI workflow. Consolidating to avoid duplicate work.


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

Closing as duplicate of #2293. This issue ("Parallelize test execution to reduce CI pipeline time") covers the same scope as #2293 ("Parallelize Nox Sessions in CI") — both aim to run independent test jobs in parallel in the CI workflow. Consolidating to avoid duplicate work. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner
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#2279
No description provided.