Bench: select custom drop-in setup for pre-install db.php mounts - #2410
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
1 participant
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
runtime.databaseSetup: custom-drop-infor explicit pre-install file mounts at/wordpress/wp-content/db.phpCloses #2409.
Verification
npx tsx tests/recipe-builder-bench-steps.test.tsnpm run buildgit diff --checknpm run smoke -- --all --concurrency=8completed all declared checks and all 328 parallel discovered files without a reported failure; the command exceeded the 10-minute local timeout during the 9-file serial integration tail, so the full smoke gate is not claimed as completeAI Assistance
GPT-5.6 Sol via OpenCode traced the custom database bootstrap failure, implemented the bounded recipe-lowering fix, added coverage, and ran verification under my direction.