Open mikkolukas opened 3 months ago
@alf4712, @zokistale, @ZayRTun, @BlackBlex, @v1p3r75
Did you ever find a solution?
I can confirm the issue have existed since pest 2.0.1, which is the version where brianium/paratest was introduced.
It turns out the bug is actually with paratestphp/paratest. I have created a bug report paratestphp/paratest#858 there too.
It bugs me though, that pestphp/pest have not created a bug report about it, as it makes noise in the pestphp/pest camp.
I've tried replicating this using your replication example, and was unable to on my macOS, Windows, or Ubuntu environments.
But I think as this is a Paratest issue, not a Pest issue, it's good to solve it there. Thanks for opening an issue in their repository. 👍🏻
@alf4712, @zokistale, @ZayRTun, @BlackBlex, @v1p3r75
Did you ever find a solution?
run "composer update" three times and all is fine. I know, it is not a solution but a workaround.
This bug have just been fixed one hour ago in paratestphp/paratest 7.5.0
That same release is completely dropping Windows support. Tagging @nunomaduro here.
If this looks familiar, it is because it is a regression of #928 (or the bug was never fixed in the first place)
Running
composer clearcache
as @nunomaduro mentioned before closing the bug, does not solve the problem.We are all humans, but it is a bit embarrassing to have a testing framework of all things to fail on such a simple bug as this when it have already been addressed and closed. One could imagine that a test had been written since #928 that ensured the bug would not appear again?
What happened
How to Reproduce
composer.json:
Run:
Sample Repository
No response
Pest Version
2.34.1
PHP Version
PHP 8.3.7 (cli) (built: May 13 2024 15:28:16) (NTS)
Operation System
Linux
Notes
php -v
:composer
:lsb_release -a
: