ci: shard Node integration tests and increase browser Playwright workers - #24676
Merged
Merged
Conversation
Co-Authored-By: GPT-6 <codex@openai.com>
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Contributor
size-limit report 📦
|
Co-Authored-By: GPT-6 <codex@openai.com>
nicohrubec
changed the title
Co-Authored-By: GPT-6 <codex@openai.com>
Co-Authored-By: GPT-6 <codex@openai.com>
nicohrubec
changed the title
Restore serial browser bundling while retaining the Node integration test shards. Co-Authored-By: GPT-6 <codex@openai.com>
nicohrubec
changed the title
Generate unminified and minified debug bundles from one Rollup build, retaining a separate production build and the existing output plugin order. Co-Authored-By: GPT-6 <codex@openai.com>
nicohrubec
changed the title
Increase browser Playwright CI workers to six. Remove Node timing reports and restore the original bundle build, retaining three shards for every Node integration configuration. Co-Authored-By: GPT-6 <codex@openai.com>
nicohrubec
changed the title
Restore three Rollup processes on the existing bundle runner to measure their effect alongside the current test parallelism. Co-Authored-By: GPT-6 <codex@openai.com>
nicohrubec
changed the title
Restore serial browser bundling and retain three Node integration shards. Co-Authored-By: GPT-6 <codex@openai.com>
nicohrubec
changed the title
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit cda6116. Configure here.
Restore the previously passing configuration with three Node integration shards and original bundling. Co-Authored-By: GPT-6 <codex@openai.com>
nicohrubec
changed the title
Co-Authored-By: GPT-6 <codex@openai.com>
nicohrubec
marked this pull request as ready for review
September 25, 2026 07:43
nicohrubec
requested review from
logaretm and
msonnb
and removed request for
a team
September 25, 2026 07:43
nicohrubec
marked this pull request as draft
September 25, 2026 07:44
nicohrubec
marked this pull request as ready for review
September 25, 2026 08:18
nicohrubec
added a commit
that referenced
this pull request
Sep 25, 2026
Similar to #24676, split Cloudflare integration tests across two CI jobs. Atm this doesn't get us an overall faster wall time but as we'll soon be running more and more tests on cloudflare this could quickly become a bottleneck, getting ahead of this by doing this simple optimization. We can also always add more shards if it becomes necessary. Both shards passed. Compared with a run off develop today: | Cloudflare | Baseline | Two shards | Faster by | | --- | --- | --- | --- | | Test execution (slowest shard) | 5m56s | 3m15s | 2m41s (45%) | | **All Cloudflare jobs finished, from CI start** | **9m31s** | **6m19s** | **3m12s** | Observed timings from one run each. - Baseline: [CI run](https://github.com/getsentry/sentry-javascript/actions/runs/36110233929) · [Sentry trace](https://sentry.sentry.io/explore/traces/trace/c7cd7471a660956b591fea4f99270e09/?project=5899451) - This PR: [CI run](https://github.com/getsentry/sentry-javascript/actions/runs/36114956684) · [Sentry trace](https://sentry.sentry.io/explore/traces/trace/f2b405b0238b2a25f431bd23da2f130f/?project=5899451) Co-authored-by: GPT-6 <codex@openai.com>
This was referenced Sep 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Improve CI speed by running Node integration tests in three shards and browser Playwright with six CI workers. I am aware benchmarking in CI is quite unreliable, but I tested this multiple times yesterday and again today and speedups were quite consistent so I think we can be reasonably confident. Most of the wall time gain definitely comes from the node integration test sharding because these were a heavy bottleneck before, now end times are much more evenly distributed.
Today's run wall time from workflow start (excluding the optional SvelteKit timeout from the required-check comparison):