ci(e2e): refresh e2e timings manifest

[GiladShoham]

Automated biweekly refresh of scripts/e2e-test-timings.json from the last 12 e2e runs (64 entries drifted meaningfully). Generated by the e2e_timings_refresh scheduled workflow.

[qodo-free-for-open-source-projects]

PR Summary by Qodo

ci(e2e): refresh e2e timings manifest

🧪 Tests ⚙️ Configuration changes 🕐 Less than 10 minutes

AI Description

• Refresh per-file e2e runtime estimates from recent CI runs.
• Update the timings manifest used to balance CircleCI parallel e2e sharding.
• Add/update entries to reflect current e2e suite composition and performance drift.

Diagram

graph TD
  A["Scheduled CI workflow"] --> B["generate-e2e-timings.js"] --> C[("e2e-test-timings.json")]
  B --> D{{"CircleCI API"}}
  E["e2e_test job"] --> F["split-e2e-tests.js"] --> G["Parallel nodes"]
  F --> C
  subgraph Legend
    direction LR
    _file[("Manifest/file")] ~~~ _proc["Script/job"] ~~~ _ext{{"External"}}
  end

Loading

High-Level Assessment

The PR’s approach (periodic regeneration of a checked-in timings manifest) is appropriate given mocha/junit timing gaps and the need for deterministic, balanced sharding. For review, spot-check that new/renamed e2e files have entries and that no obviously extreme weights would skew node balance.

Files changed (1) +176 / -173

Other (1) +176 / -173

e2e-test-timings.jsonRegenerate e2e per-file timing weights from recent CI runs +176/-173

Regenerate e2e per-file timing weights from recent CI runs

• Refreshes the per-e2e-file duration estimates used for CircleCI parallel test splitting. Updates many existing weights and introduces entries for newly observed e2e test files while reflecting recent performance drift.

scripts/e2e-test-timings.json

[qodo-free-for-open-source-projects]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

_{To customize comments, go to the Qodo configuration screen, or learn more in the docs.}