You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you have pcov setup as an extension and you've also got infection setup, the infection run dies on sig 11.
Removing pcov as a required extension makes infection run normally - I guess pcov and phpdbg don't play nicely together.
If you need pcov for you project, this is a bit of pain because you can't opt-out of the infection run and write your own workflow without phpdbg because the run is triggered by the infection.json file.
In my case, I'm just gonna make do without pcov. Perhaps this is just a documentation issue. If so, it wold also be worth providing some helpful setup pointers for infection configuration WRT running this action successfully.
The text was updated successfully, but these errors were encountered:
It was this pull on a WIP pet project - I had infection running fine in my own workflows with pcov, but dropped them in favour of laminas-ci. Removing pcov from laminas-ci.json fixed the segfaults so it's just my assumption that the combination of pcov/phpdbg was the problem
I think pcov, xdebug and phpdbg should be able to coexist regardless: probably best to raise this in infection/infection and ask for further guidance there, than just dropping the dependency here.
Bug Report
Summary
If you have
pcov
setup as an extension and you've also got infection setup, the infection run dies on sig 11.Removing pcov as a required extension makes infection run normally - I guess pcov and phpdbg don't play nicely together.
If you need pcov for you project, this is a bit of pain because you can't opt-out of the infection run and write your own workflow without phpdbg because the run is triggered by the infection.json file.
In my case, I'm just gonna make do without pcov. Perhaps this is just a documentation issue. If so, it wold also be worth providing some helpful setup pointers for infection configuration WRT running this action successfully.
The text was updated successfully, but these errors were encountered: