Symfony 4代码贡献遇阻：未修改代码即出现大量测试失败问题

Let’s walk through the common issues and fixes for the test failures you’re seeing after switching to PHP 7.2 for your Symfony 4 contribution work:

• Adjust error reporting to ignore deprecation notices
  Symfony 4 fully supports PHP 7.2, but the "Other deprecation notices" failures typically happen because PHPUnit is treating deprecation warnings as blocking errors. You can fix this in two ways:

  • Edit the project’s phpunit.xml.dist file, add or update this section under the <php> tag to suppress deprecation-related warnings:

    <ini name="error_reporting" value="E_ALL & ~E_DEPRECATED & ~E_USER_DEPRECATED"/>
    

  • Or run your test command with a temporary error reporting override:

    php ./phpunit symfony -d error_reporting="E_ALL & ~E_DEPRECATED & ~E_USER_DEPRECATED"
    

• Target specific components for testing
  The command php ./phpunit symfony might be targeting a broad or incorrect test scope. If you’re focusing on the Messenger component (as mentioned in your error), run tests for that component specifically instead:

  php ./phpunit src/Symfony/Component/Messenger/
  

  This narrows down the test suite and avoids unrelated deprecation notices from other parts of the codebase.

• Refresh dependencies after switching PHP versions
  Switching PHP versions can leave stale autoloader entries or mismatched dev dependencies. Run these commands to ensure everything is aligned with your current PHP environment:

  composer clear-cache
  composer install --dev
  

  This will reinstall PHPUnit and other dev tools tailored to PHP 7.2.

• Confirm you’re on the correct Symfony 4 branch
  Make sure you’re working on the Symfony 4.4 branch (the LTS release for Symfony 4) rather than newer branches like 5.x or 6.x. Newer branches use PHP features incompatible with 7.2, which would trigger unexpected deprecation notices or errors.

内容的提问来源于stack exchange，提问作者fishbone