Summary
A managed wordpress.phpunit run configured with MySQL and multisite boots WordPress without creating the required multisite network tables. PHPUnit continues, but WordPress emits database errors for wptests_blogs and wptests_sitemeta, so multisite behavior cannot be validated faithfully.
Evidence
Runtime configuration:
{
"database_type": "mysql",
"validation_dependencies": [
{ "type": "local", "path": "<checkout>/.ci/data-machine", "plugin_slug": "data-machine", "activate": true },
{ "type": "local", "path": "<checkout>/.ci/data-machine-events", "plugin_slug": "data-machine-events", "activate": true }
],
"wp_codebox_multisite": true,
"wp_codebox_phpunit_bootstrap_mode": "managed"
}
Exact startup diagnostics:
WordPress database error Table 'runtime.wptests_blogs' doesn't exist for query SELECT wptests_blogs.blog_id ... made by pg_run_install_stage, ... wp-phpunit/includes/install.php, ... ms_load_current_site_and_network
WordPress database error Table 'runtime.wptests_sitemeta' doesn't exist for query SELECT meta_value FROM wptests_sitemeta ... made by pg_run_install_stage, ... wp-phpunit/includes/install.php, ... get_network_option
WordPress database error Table 'runtime.wptests_blogs' doesn't exist for query SELECT * FROM wptests_blogs WHERE blog_id = 1 LIMIT 1 ... ms_site_check, get_site, WP_Site::get_instance
The managed suite then reports 276 tests, but current-site lookups and every network option operation are running against an incomplete schema.
Expected
When multisite is enabled, the managed install stage creates and seeds at least the standard blogs, blogmeta, site, sitemeta, registration_log, and signups tables before WordPress multisite bootstrap and plugin activation.
Impact
Consumers cannot establish a real managed MySQL/multisite PHPUnit baseline. Adding per-test cache objects or bypassing get_site() would hide the broken runtime and would not validate multisite behavior.
Summary
A managed
wordpress.phpunitrun configured with MySQL and multisite boots WordPress without creating the required multisite network tables. PHPUnit continues, but WordPress emits database errors forwptests_blogsandwptests_sitemeta, so multisite behavior cannot be validated faithfully.Evidence
6aa2b97cd4170cc6a3d2e350d316541547f35a7d1cd18d310.314.2+bbf556096619+cb0497a8.3.32managedRuntime configuration:
{ "database_type": "mysql", "validation_dependencies": [ { "type": "local", "path": "<checkout>/.ci/data-machine", "plugin_slug": "data-machine", "activate": true }, { "type": "local", "path": "<checkout>/.ci/data-machine-events", "plugin_slug": "data-machine-events", "activate": true } ], "wp_codebox_multisite": true, "wp_codebox_phpunit_bootstrap_mode": "managed" }Exact startup diagnostics:
The managed suite then reports 276 tests, but current-site lookups and every network option operation are running against an incomplete schema.
Expected
When multisite is enabled, the managed install stage creates and seeds at least the standard
blogs,blogmeta,site,sitemeta,registration_log, andsignupstables before WordPress multisite bootstrap and plugin activation.Impact
Consumers cannot establish a real managed MySQL/multisite PHPUnit baseline. Adding per-test cache objects or bypassing
get_site()would hide the broken runtime and would not validate multisite behavior.