Trigger warning when code coverage analysis is performed and no cache directory is configured

[sebastianbergmann]

No description provided.

[Zolletta]

So you are meaning that cache is mandatory for code coverage analysis?

Thank you

[chamithmalindalsc]

We got this issue in our pipelines suddenly 2 days back. Had to update the cache directory to get this working and it's wired.

     `cacheDirectory=".phpunit.cache"`

following is the warning. But this was not there 2,3 days back - strange

WARN No cache directory configured, result of static analysis for code coverage will not be cached

[spawnia]

I have had a couple CI pipelines fail as a result of this change. Perhaps this warning is a bit overzealous?

My solution attempt at a solution was to set failOnWarning="false" in my PHPUnit XML configuration, e.g.

<?xml version="1.0"?>
<phpunit failOnWarning="false"

Configuring cacheDirectory, as described in #6150 (comment) did the trick. However, I feel that this adds a line of boilerplate that I did not necessarily need before to every project.

Why do I need to change my configuration now when it used to work fine before? What is the proper resolution for this?

[Zolletta]

@sebastianbergmann I see now that the trigger is a phpunit 12.1 milestone. But I am currently using version 11. Maybe you can raise the trigger warning only if the version is 12 or (12.1) or above?

[sebastianbergmann]

Those two changes are unrelated. I have reverted the warning in PHPUnit 11.5 and PHPUnit 12.0.

[mvorisek]

+1 for reverting the warning as pointed out in 6565fa7#r154096373

landed/reverted in 82c0b24

Please never require explicit cache directory. Implicit system cache directory should be used instead when accessible. The reason is we want to keep our configs minimal as possible.

@sebastianbergmann would you mind to tag a new releases with the revert?