Review Checklist

• Target branch (11.2 for bug fixes, others 11.x)
• Tests (if it's testable code, there should be a test for it - get help)
• Docs (every functionality needs to be documented, see here)
• Migration incl. install.sql (e.g. if the database schema changes, ...)
• Upgrade notes (deprecations, important information, migration hints, ...)
• Label
• Milestone

Can you please check if symfony/symfony#57615 fixes your tests?

@derrabus Thank you for coming by, but i can't test it because it's likely unrelated (fails with 7.1.1) to that.
It still seems related to some "regression" in the latest release, because our lowest tests are working fine, but highest started failing in these 3 days which matches with the latest symfony bugfix release

No idea why but the latest bugfix release of symfony/http-client breaks our tests

@markus-moser You mean symfony/http-kernel
It must be this PR then: symfony/symfony#57553

The PR symfony/symfony#57372 is too old. Then the tests must have failed for 2 weeks (there is a 6.4.x test).

@blankse Yes I also thought that this PR can be the only reason.

@markus-moser I can confirm that it is this PR. When I locally revert these changes, the tests run correctly.

Maybe is the error here:
https://github.com/pimcore/pimcore/blob/11.x/lib/Translation/Translator.php#L390
The internal translator has a new second argument $buildDir

https://github.com/pimcore/pimcore/blob/11.x/lib/Translation/Translator.php#L390

Thanks for the hint - yes this sounds like it could be the cause of the problem

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

It's a bit weird but works now.

The fallback language was not actually defined in the system settings of the tests. So it only worked by some kind of side effect. Maybe because of the order of the tests and this configuration change in the localized field test

If the HttpKernel change causes issues, could you please check if symfony/symfony#57593 is of any help?

@xabbuh Thanks for your hint but we found out that a problem in our test setup was the root cause of the problem.