Skip to content
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

Infection always fails if you want pcov installed #91

Open
gsteel opened this issue Apr 26, 2022 · 3 comments
Open

Infection always fails if you want pcov installed #91

gsteel opened this issue Apr 26, 2022 · 3 comments
Labels
Bug Something isn't working

Comments

@gsteel
Copy link
Member

gsteel commented Apr 26, 2022

Bug Report

Q A
Version(s) latest

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.

@gsteel gsteel added the Bug Something isn't working label Apr 26, 2022
@Ocramius
Copy link
Member

Which project experiences this? I use pcov for MT all the time 🤔

@gsteel
Copy link
Member Author

gsteel commented Apr 26, 2022

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

@Ocramius
Copy link
Member

Crash @ https://github.com/gsteel/listless/runs/6182805668?check_suite_focus=true#step:3:427

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants