Closed bocharsky-bw closed 1 month ago
Well, seems it helped, see the prove in https://github.com/SymfonyCasts/tailwind-bundle/actions/runs/11500343719/job/32010355575?pr=74
1) Symfonycasts\TailwindBundle\Tests\TailwindBuilderTest::testBuildProvidedInputFile
Could not remove the temporary tailwind/ dir from the time: Failed to remove file "D:\a\tailwind-bundle\tailwind-bundle\tests/fixtures/var/tailwind\v3.4.14\tailwindcss-windows-x64.exe": unlink(D:\a\tailwind-bundle\tailwind-bundle\tests/fixtures/var/tailwind\v3.4.14\tailwindcss-windows-x64.exe): Permission denied
D:\a\tailwind-bundle\tailwind-bundle\vendor\phpunit\phpunit\src\Framework\TestResult.php:728
D:\a\tailwind-bundle\tailwind-bundle\vendor\phpunit\phpunit\src\Framework\TestSuite.php:684
D:\a\tailwind-bundle\tailwind-bundle\vendor\phpunit\phpunit\src\Framework\TestSuite.php:684
D:\a\tailwind-bundle\tailwind-bundle\vendor\phpunit\phpunit\src\Framework\TestSuite.php:684
D:\a\tailwind-bundle\tailwind-bundle\vendor\phpunit\phpunit\src\TextUI\TestRunner.php:653
WARNINGS!
Tests: 7, Assertions: 19, Warnings: 1.
@MolloKhan what do you think?
If the file paths with mixed slashes /
\
are not the issue, I'd try to remove the tailwind
folder in the teardown
method instead of setup()
, so everything will happen during the same test. I mean, the folder will be created and deleted during the lifecycle of each test. That may help with permissions but I'm guessing
@MolloKhan I created a competitor PR for that in #75, let's see
Close in favor of #75
Sometimes we have random test failures on Windows, see https://github.com/SymfonyCasts/tailwind-bundle/actions/runs/11490280966/job/31980693499
Probably this will help? Thoughts?
I think this may help