Skip to content

fix(tests): cross the large-array threshold with 64 wide rows instead of 120k - #8939

Merged
waleedlatif1 merged 1 commit into
stagingfrom
fix/execute-request-test-timeout
Oct 12, 2026
Merged

waleedlatif1 merged 1 commit into
stagingfrom
fix/execute-request-test-timeout

Conversation

@waleedlatif1

Copy link
Copy Markdown
Collaborator

Summary

execute-request.test.ts > compacts large array result fields to manifests when execution context is durable timed out at 10s in CI (run 38300495470, checks / test (1/2)).

It built 120,000 small rows (~16 MB). Compaction does a promise plus several JSON.stringify calls for every row, so its cost grows with the number of rows, not their total size. On healthy runners the test took 575–1,522 ms (median 743 ms) and was always the slowest test in the file. On a contended runner it took 10.6s.

The test now returns 64 rows whose payloads add up to LARGE_VALUE_THRESHOLD_BYTES. The array is just over the threshold and each row is well under it, so it exercises the same path: an array over the threshold in a durable context becomes a manifest. The assertions are unchanged except that totalCount now equals rowCount. Across the last 100 ci runs this was the only failure of the test. No timeout was raised.

Test plan

  • CI test shards: the case passes, in well under the old ~0.7s median

… of 120k

The durable-manifest test built 120,000 small rows (~16 MB). Compaction
walks every element (a promise, Object.entries and JSON.stringify per row
and per field), so the test ran 575-1522 ms on healthy CI runners and
10.6 s on a contended one, timing out. 64 rows whose payloads sum to
LARGE_VALUE_THRESHOLD_BYTES cross the same threshold with the same
assertions; the 9 MB string tests beside it run in ~50 ms.
@vercel

vercel Bot commented Oct 12, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated
docs Skipped Skipped Oct 12, 2026 8:07pm UTC

Request Review

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

Confidence score: 5/5

  • Automated review surfaced no issues in the provided summaries.
  • No files require special attention.

Heads up: you’ve reached your flex budget. Increase your flex budget or wait for usage to reset.

Turn on auto-fix | Re-trigger cubic

@greptile-apps

greptile-apps Bot commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor

RetriggerConfidence Score: 5/5

[Low impact] This PR appears safe to merge; the smaller fixture still exercises the intended large-array path.

Summary

This PR makes the large-array test cheaper without changing production code.

  • The durable execution test reaches the array limit with 64 wide rows.

Reviews (1) · Last reviewed commit: "fix(tests): cross the large-array thresh..." · Reviewed by Greptile

@waleedlatif1
waleedlatif1 merged commit bf87c51 into staging Oct 12, 2026
48 checks passed
@waleedlatif1
waleedlatif1 deleted the fix/execute-request-test-timeout branch October 12, 2026 20:36

This branch was previously deployed

1 inactive deployment
Preview — 30501d91 Deployed Oct 12, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant