Closed garak closed 1 month ago
I'm not sure this is an issue with Paraunit: the trigger is in our extension, but the stack trace shows that the issue is with mkdir
, which is triggering a silenced error when the dir already exist, then afterwards PHPUnit's error handler is trying to find a test case which is not there.
It should probably be fixed either in PHPUnit or the Symfony error handler, which is probably interfering with PHPUnit's.
The point is that with the bridge 7.1 (and the same version of PHPUnit), tests run fine when I don't use paraunit. I have the exception only when I do use paraunit.
Oh, and now things start to become funny: if I upgrade the other symfony components from 6.4.7 to 6.4.8 I get the same exception in paraunit (but, again simple phpunit works). If I downgrade them back to 6.4.7, it works 😕
I better isolated the problem and found that symfony/phpunit-bridge 7.0.8 gives the same exception.
Maybe the culprit is the change made in this PR https://github.com/symfony/symfony/pull/54797
That's not the proper culprit, just the trigger. IMHO the issue is in the PHPUnit error handler, that thinks that it's invoked always inside a test. I'll try to create a reproducer.
[EDIT] I cannot reproduce. I think you should report this to Symfony.
I've tried to reproduce this to report to Symfony, but I noticed that I could simply fix it. #250 is now released as 2.3.3
Symfony released version 7.1 today, so I upgraded a project of mine ( the project uses Symfony 6.4, and Symfony 7 for the bridge only).
Tests are broken with the following exception. Downgrading to Symfony 7.0 makes them working again: