-
-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove phpdbg
, migrate to pcov
#130
Comments
PHPDBG support has been removed right now: sebastianbergmann/php-code-coverage@c304be7 |
PHPUnit 10 pulled the plug and switched over: will prepare a patch for this, since we can otherwise no longer run coverage reports (which breaks mutation tests) |
This is a potential breaking change, but note that PHPUnit v10 no longer supports PHPDBG for coverage, which was the only use-case for PHPDBG in this container, thus far. We instead install `pcov`, which is considered precise enough for coverage reports by PHPUnit. Fixes laminas#130 Ref: laminas#130 Ref: sebastianbergmann/php-code-coverage#945 Ref: sebastianbergmann/php-code-coverage@c304be7
I still lack time/mood to combine matrix + action in one repository as I am still not that deep into the whole container registry push stuff, etc. This change will introduce BC break to almost any project running infection.
|
Same: mostly trying to reduce the dependency upgrade noise caused by PHPUnit 10.
I will go for
If we roll |
Only thing I don't like about this is that this will then lead to upgrade maintenance in all repositories, including those which still have support for 7.4 which then have to release with a new version dropping 7.4 just because we dropped it as some extension is not properly installable in docker. So I know that dropping old PHP versions usually provide "easy fixes" but since we are providing a CI pipeline here, it feels kinda weird that we start dropping "old" PHP versions. I still think it could be possible to have both phpdbg and pcov available, might just be a problem with enabling the pcov extension for the dbg SAPI which can probably be fixed in here: Anyways, thats not the time to discuss this further. I'm fine with a new release - lets see how it will end. Maybe I'm just the panicking dude again while there is no reason to cry. 😅 |
Well, 7.x is gonna be in oldstable anyway, no? The fact that we keep this to a new major is OK IMO 👍 I just need to find the willpower to coordinate the releases xD |
…pcov Removed `phpdbg`, added `pcov` dependency as part of the build
See laminas/laminas-continuous-integration-action#130 Signed-off-by: George Steel <george@net-glue.co.uk>
…-action#130 is finished Signed-off-by: George Steel <george@net-glue.co.uk>
Hello, same question as @Slamdunk , can it be release ? thanks |
This patch reduces code size, therefore leading to generally lower scores. Until we completely switch to `pcov` and the upstream issues with `sebastianbergmann/php-code-coverage` are resolved, we will keep having sub-100% mutation test scores. Ref: sebastianbergmann/php-code-coverage#945 Ref: sebastianbergmann/php-code-coverage@c304be7 Ref: laminas/laminas-continuous-integration-action#130 Ref: sebastianbergmann/php-code-coverage#953
See sebastianbergmann/php-code-coverage#945
According to upstream maintainers,
phpdbg
coverage support is not really maintained, and we should therefore migrate away from it.We will likely need to ship
pcov
with our container, and use that for running tests.We may also need to remove
phpdbg
, since runningphpdbg
withpcov
installed leads to segfaults.The text was updated successfully, but these errors were encountered: