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

Removed phpdbg, added pcov dependency as part of the build #148

Merged

Conversation

Ocramius
Copy link
Member

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 #130

Ref: #130
Ref: sebastianbergmann/php-code-coverage#945
Ref: sebastianbergmann/php-code-coverage@c304be7

Q A
Documentation no
Bugfix yes
BC Break yes (?)
New Feature yes
RFC no
QA yes

Only question here is:

  • do we release on 1.33.0?
  • do we release on 2.0.0?

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
@Ocramius
Copy link
Member Author

 #13 36.03 E: Unable to locate package php5.6-pcov
#13 36.03 E: Couldn't find any package by glob 'php5.6-pcov'
#13 36.03 E: Unable to locate package php7.0-pcov
#13 36.03 E: Couldn't find any package by glob 'php7.0-pcov'

Nnnnngh... gonna revert for those two...

@internalsystemerror
Copy link
Member

I'm guessing we can't use PHPUnit 10 on those PHP versions anyway. 2.0.0 sounds like the safer bet for people who are actively using this.

@gsteel
Copy link
Member

gsteel commented Feb 22, 2023

I'm in favour of 1.33.0 FWIW - It's just a change in dependencies rather than an alteration to behaviour. The action will still do all of the things it was supposed to, in effectively the same way right?

entrypoint.sh Show resolved Hide resolved
@internalsystemerror
Copy link
Member

The action will still do all of the things it was supposed to, in effectively the same way right?

If you were depending on phpdbg before, you won't be able to now.

@boesing
Copy link
Member

boesing commented Feb 22, 2023

#130 (comment)

@Ocramius Ocramius modified the milestones: 1.33.0, 2.0.0 Feb 22, 2023
@Ocramius
Copy link
Member Author

This will go to 2.0.0, but I need to verify that pcov is enabled by default, before merging.

@Ocramius Ocramius self-assigned this Feb 22, 2023
@Ocramius Ocramius changed the base branch from 1.33.x to 2.0.x March 2, 2023 15:33
@Ocramius Ocramius merged commit e9cfefa into laminas:2.0.x Mar 2, 2023
@Ocramius Ocramius deleted the fix/#130-switch-from-phpdbg-to-pcov branch March 2, 2023 15:36
@Ocramius
Copy link
Member Author

Ocramius commented Mar 2, 2023

Since @lcobucci is starting to get blocked by this quite a bit, I'm trying to push it forward :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BC Break dependencies Pull requests that update a dependency file Enhancement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Remove phpdbg, migrate to pcov
4 participants