Repository navigation
Split the Behat tests with code coverage across runners - #316
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…pport Every runner spends about a minute on its setup, so packages now get one coverage runner per 50 scenarios, up to the coverage-shards input. Versions of wp-cli/wp-cli-tests without sharding support ignore WP_CLI_TEST_SHARD and would run every scenario on every shard. With those, only the first shard runs the scenarios, so that each still runs once. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
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
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.
The Behat job with code coverage ran every scenario one after the other under Xdebug, and took most packages far longer than any other job. In wp-cli/wp-cli it took 45–48 min, while every other job finished in under 6.
Changes
coverage-driverinput. PCOV only instruments the files underpcov.directory, set to the checkout. Xdebug instruments every file PHP loads, all of WordPress included. PCOV alone halved the job time.WP_CLI_TEST_SHARD, each runner with 4 parallel workers.coverage-shardsinput (default 4), because every runner spends about a minute on its setup.coverage_shards.after_n_builds: 2keep working.Results in wp-cli/wp-cli
Measured with wp-cli/wp-cli-tests#420:
globalstatements, which Xdebug counts and PCOV doesn't.actionlint is clean.
🤖 Generated with Claude Code