Skip to content

Build/Test Tools: Trim the PHPUnit matrix to boundary PHP versions on the 7.0 branch - #12720

Closed
lancewillett wants to merge 1 commit into
WordPress:7.0from
lancewillett:trim-7.0-phpunit-matrix
Closed

Build/Test Tools: Trim the PHPUnit matrix to boundary PHP versions on the 7.0 branch#12720
lancewillett wants to merge 1 commit into
WordPress:7.0from
lancewillett:trim-7.0-phpunit-matrix

Conversation

@lancewillett

Copy link
Copy Markdown
Contributor

What

Trims the PHPUnit test matrix on the 7.0 branch to boundary PHP versions: 7.4, 8.0, and 8.5 in place of the full seven-minor list, across test-with-mysql, test-with-mariadb, and test-innovation-releases.

Why

This applies to the 7.0 branch the same boundary trim #64083 used on older branches (Trac #65736 tracks extending it to the current branches). The immediate benefit is at release time. When many 7.0.x backports land together, the full matrix floods the shared runner pool. Tests get cancelled, or the release ships before they finish.

Impact

Base PHPUnit combinations drop from ~168 to ~72 per run, roughly a 55% cut, before the unchanged include: jobs.

Scope

PHP axis only. The 7.0 branch does not run the weekly scheduled full matrix. Scheduled workflows fire only from the default branch. So this is a plain trim, not the conditional used on trunk. Database versions, multisite, and memcached are untouched.

Trac ticket: Core-65736

Use of AI Tools

AI assistance: Yes
Tool(s): Claude Code
Model(s): Opus 4.8
Used for: Applying the boundary-trim approach from the existing older-branch precedent. Verified manually.

Reduce the PHPUnit matrix on the active branch to the highest and lowest supported version of each major PHP branch, matching the boundary testing already used on older branches. Version-specific failures cluster at the boundaries, so the intermediate minor versions add job count without adding coverage.

This is especially useful when preparing backports across multiple branches, where the full matrix multiplies queued jobs and floods the shared runner pool during a release.

Props lance.willett@automattic.com.

See #65736.
@github-actions

Copy link
Copy Markdown

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props lancewillett.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

pento pushed a commit that referenced this pull request Jul 27, 2026
… the 7.0 branch.

This reduces the number of jobs that get triggered for each push or PR to the branch while retaining testing on the highest and lowest supported versions of PHP.

Developed in #12720

Props lancewillett, adrianmoldovanwp

See #65736, #64083


git-svn-id: https://develop.svn.wordpress.org/branches/7.0@62856 602fd350-edb4-49c9-b593-d223f7449a82
@johnbillion

Copy link
Copy Markdown
Member

markjaquith pushed a commit to markjaquith/WordPress that referenced this pull request Jul 27, 2026
… the 7.0 branch.

This reduces the number of jobs that get triggered for each push or PR to the branch while retaining testing on the highest and lowest supported versions of PHP.

Developed in WordPress/wordpress-develop#12720

Props lancewillett, adrianmoldovanwp

See #65736, #64083

Built from https://develop.svn.wordpress.org/branches/7.0@62856


git-svn-id: http://core.svn.wordpress.org/branches/7.0@62136 1a063a9b-81f0-0310-95a4-ce76da25c4cd
@lancewillett

Copy link
Copy Markdown
Contributor Author

See also: #12726

6.8 runs were still peaking at ~198, this takes that version's runs down to ~99.

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.

3 participants