If nesting kernels, the same instance of ConfigLoader is used for both kernels. The result is that if there were any runtime changes to configuration (i.e. MyClass::config()->set()), these changes are discarded for both kernels.
For production scenarios this isn't likely to cause problems, because runtime configuration changes are probably made inside _config.php files which are also re-executed, but for unit tests this can cause problems as seen in https://github.com/silverstripe/silverstripe-staticpublishqueue/pull/178
If nesting kernels, the same instance of
ConfigLoaderis used for both kernels. The result is that if there were any runtime changes to configuration (i.e.MyClass::config()->set()), these changes are discarded for both kernels.For production scenarios this isn't likely to cause problems, because runtime configuration changes are probably made inside
_config.phpfiles which are also re-executed, but for unit tests this can cause problems as seen in https://github.com/silverstripe/silverstripe-staticpublishqueue/pull/178Issue