fix: support wp-cli bench workloads#332
Merged
Merged
Conversation
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.
Summary
wordpress.benchworkload steps oftype: "wp-cli"through the existing runtime WP-CLI bridge instead of trying to load WP-CLI inside the active bench PHP process.wordpress.wp-cliin recipe policy when awordpress.benchrecipe includes configured WP-CLI workload steps.Testing
npm run buildnpm run recipe-bench-smokenpm run recipe-dry-run-smokenpm run discovery-command-smokegit diff --checkAI assistance
wordpress.benchWP-CLI workload crash, drafted the bridge-based runtime/policy changes, and ran focused local verification. Chris remains responsible for review and merge.