…s (ogizanagi)This PR was merged into the 3.4 branch.Discussion----------[FrameworkBundle] Register a NullLogger from test kernels| Q             | A| ------------- | ---| Branch?       | 3.4 <!-- see comment below -->| Bug fix?      | no| New feature?  | no <!-- don't forget updating src/**/CHANGELOG.md files -->| BC breaks?    | no| Deprecations? | no <!-- don't forget updating UPGRADE-*.md files -->| Tests pass?   | yes| Fixed tickets | N/A <!-- #-prefixed issue number(s), if any -->| License       | MIT| Doc PR        | N/ARelates to#24300This will avoid unnecessary output on Travis or when running FrameworkBundle tests locally:- before:https://travis-ci.org/symfony/symfony/jobs/281624658#L3594-L3635- after:https://travis-ci.org/symfony/symfony/jobs/281643868#L3599-L3617but also needed for anyone running functional tests on their project and using the default logger, in order to not get garbage output.Do we need to find a more generic solution (like exposing a `framework.default_logger` option so users can set it to false for test)? Or just documenting this?Commits-------c109dcd [FrameworkBundle] Register a NullLogger from test kernels

This PR was merged into the 1.x-dev branch.Discussion----------Update symfony 4 compatibilityTODO:- [x] Update tests to use new PHPUnit namespaces- [x] Fix phpunit version used through env var- [x] Inject a `NullLogger` (seesymfony/symfony#24385)Commits-------64fc69d Use new PhpUnit namespacesa4705a5 Inject a NullLogger for integration tests46e775c Moar travis changese438be5 Update symfony 4 compatibility