Skip to content

DO NOT MERGE: wp-build concurrency test (WordPress/gutenberg#79889) - #53394

Closed
louwie17 wants to merge 4 commits into
trunkfrom
test/wp-build-concurrency-79889
Closed

louwie17 wants to merge 4 commits into
trunkfrom
test/wp-build-concurrency-79889

Conversation

@louwie17

@louwie17 louwie17 commented Oct 9, 2026

Copy link
Copy Markdown
Contributor

Do not merge. A measurement PR for WordPress/gutenberg#79889, which limits how many esbuild builds @wordpress/build runs at once.

Proposed changes

  • This is the experiment. Overrides @wordpress/build with Gutenberg 1da05f7 (the head of Limit wp-build esbuild concurrency WordPress/gutenberg#79889), following this suggestion. Its pair is DO NOT MERGE: wp-build concurrency test (control) #53393 (control). Both branches share the same base commit and differ only in this SHA.
  • @wordpress/build>@wordpress/style-runtime and @wordpress/build>@wordpress/browserslist-config are pinned to their published 0.13.0 and 6.57.0. wp-build depends on them via file:../, which does not resolve from a git subdirectory, and the git copy of style-runtime has no built files.
  • blockExoticSubdeps: false and allowBuilds: '@wordpress/build': false are needed for the git-hosted package.
  • Temporary CI instrumentation (same commit in both PRs): .github/files/build-memory-sampler.sh samples system memory, the build's process-tree RSS and process count every 2 seconds during the build jobs. Each build job writes a "Build memory" table to its run summary and uploads a build-memory-<job> artifact with the CSV and a process snapshot at the peak.

Related product discussion/links

Does this pull request change what data or activity we track or use?

No.

Testing instructions

  • Compare the "Build all projects" / "Build wpcom projects" / "Build non-wpcom projects" jobs of this PR with DO NOT MERGE: wp-build concurrency test (control) #53393 (control): step duration of "Build changed projects", and the "Build memory" table in each run summary.
  • The experiment's build log prints Using build concurrency: <n> for each wp-build package. The control prints nothing.

🤖 Generated with Claude Code

https://claude.ai/code/session_016X2tCG3bAWBcoLA8VjvnXd

louwie17 and others added 2 commits October 9, 2026 09:46
Samples system memory, build-tree RSS and process count every 2 seconds
during the build jobs, writes a summary to the job page and uploads the
CSV. For measuring WordPress/gutenberg#79889; do not merge.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016X2tCG3bAWBcoLA8VjvnXd
Overrides @wordpress/build with the PR head (1da05f7) to measure its
esbuild concurrency limit in CI. Do not merge.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016X2tCG3bAWBcoLA8VjvnXd
@github-actions

github-actions Bot commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

  • To test on WoA, go to the Plugins menu on a WoA dev site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin (Jetpack or WordPress.com Site Helper), and enable the test/wp-build-concurrency-79889 branch.
  • To test on Simple, run the following command on your sandbox:
bin/jetpack-downloader test jetpack test/wp-build-concurrency-79889
bin/jetpack-downloader test jetpack-mu-wpcom-plugin test/wp-build-concurrency-79889

Interested in more tips and information?

  • In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
  • Read more about our development workflow here: PCYsg-eg0-p2
  • Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

@github-actions github-actions Bot added [Status] In Progress Actions GitHub actions used to automate some of the work around releases and repository management labels Oct 9, 2026
@github-actions

github-actions Bot commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

  • ✅ Include a description of your PR changes.
  • ✅ Add a "[Status]" label (In Progress, Needs Review, ...).
  • ✅ Add testing instructions.
  • ✅ Specify whether this PR includes any changes to data or privacy.
  • ✅ Add changelog entries to affected projects

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖


Follow this PR Review Process:

  1. Ensure all required checks appearing at the bottom of this PR are passing.
  2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
  3. You can use GitHub's Reviewers functionality to request a review.
  4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!

@github-actions github-actions Bot added the [Status] Needs Author Reply We need more details from you. This label will be auto-added until the PR meets all requirements. label Oct 9, 2026
@jp-launch-control

jp-launch-control Bot commented Oct 9, 2026 •

Copy link
Copy Markdown

Code Coverage Summary

This PR did not change code coverage!

That could be good or bad, depending on the situation. Everything covered before, and still is? Great! Nothing was covered before? Not so great. 🤷

Full summary · PHP report · JS report

@louwie17 louwie17 closed this Oct 22, 2026
@github-actions github-actions Bot removed [Status] Needs Author Reply We need more details from you. This label will be auto-added until the PR meets all requirements. [Status] In Progress labels Oct 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Actions GitHub actions used to automate some of the work around releases and repository management

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant