You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
When executing functional tests in Symfony 4.4 and 5.0, a new container initialization and dump is done for each test. This makes the overall test suite take a lot more time to complete (we have approximately 300 test running in our CI and it breaks the 1 hour limit when before it was taking no more than 14 minutes), in previous versions it was working fine. After the first time executing the tests (and if no change has been made that could cause a new container dump), it continues to work correctly.
This seems to be caused by the changes introduced in this commit: 7f9556c
For what I can see, as now the cache is checked only once per process, it keeps being not fresh even though a new container has already been initialized.
How to reproduce
This problem can be reproduced using the demo Symfony application (upgrading it to v4.4.0).
Possible Solution
The easier solution would be to mark the cache as fresh just after dumping the container here:
Symfony version(s) affected:
4.4.0
5.0.0
Description
When executing functional tests in Symfony 4.4 and 5.0, a new container initialization and dump is done for each test. This makes the overall test suite take a lot more time to complete (we have approximately 300 test running in our CI and it breaks the 1 hour limit when before it was taking no more than 14 minutes), in previous versions it was working fine. After the first time executing the tests (and if no change has been made that could cause a new container dump), it continues to work correctly.
This seems to be caused by the changes introduced in this commit: 7f9556c
For what I can see, as now the cache is checked only once per process, it keeps being not fresh even though a new container has already been initialized.
How to reproduce
This problem can be reproduced using the demo Symfony application (upgrading it to v4.4.0).
Possible Solution
The easier solution would be to mark the cache as fresh just after dumping the container here:
symfony/src/Symfony/Component/HttpKernel/Kernel.php
Lines 553 to 555 in 7719fc7
The text was updated successfully, but these errors were encountered: