Skip to content

Bump PHPUnit to 10.5.60#42

Merged
theseer merged 3 commits intotheseer:mainfrom
staabm:uo
Dec 6, 2025
Merged

Bump PHPUnit to 10.5.60#42
theseer merged 3 commits intotheseer:mainfrom
staabm:uo

Conversation

@staabm
Copy link
Contributor

@staabm staabm commented Dec 6, 2025

closes #40

➜  tokenizer git:(uo)  ./tools/phpunit
PHPUnit 10.5.60 by Sebastian Bergmann and contributors.

Runtime:       PHP 8.3.28
Configuration: /Users/staabm/workspace/tokenizer/phpunit.xml

........................                                          24 / 24 (100%)

Time: 00:00.005, Memory: 22.97 MB

There was 1 PHPUnit test runner warning:

1) No code coverage driver available

OK, but there were issues!
Tests: 24, Assertions: 31, PHPUnit Warnings: 1, PHPUnit Deprecations: 1.

@staabm staabm marked this pull request as ready for review December 6, 2025 09:05
@staabm
Copy link
Contributor Author

staabm commented Dec 6, 2025

I don't get why in CI we get

Error: No matching release found for phpunit!

while locally I was able to install PHPUnit

➜  tokenizer git:(uo) tools/phpunit --version
PHPUnit 10.5.60 by Sebastian Bergmann and contributors.

(in CI phive results are different based on php version. in some jobs it works like expected in others it reports "no matching release", in others there are some gpg errors)

@theseer
Copy link
Owner

theseer commented Dec 6, 2025

Run ./tools/phpunit
PHPUnit 10.5.60 by Sebastian Bergmann and contributors.

Runtime:       PHP 8.3.28
Configuration: /home/runner/work/tokenizer/tokenizer/phpunit.xml

........................                                          24 / 24 (100%)

Time: 00:00.009, Memory: 22.96 MB

There was 1 PHPUnit test runner warning:

1) No code coverage driver available

OK, but there were issues!
Tests: 24, Assertions: 31, PHPUnit Warnings: 1.
Error: Process completed with exit code 1.

I'm not sure why it exits with "code 1"? Having no coverage driver should not be a problem - or should it?

@theseer theseer merged commit cb7e1e6 into theseer:main Dec 6, 2025
0 of 12 checks passed
@staabm
Copy link
Contributor Author

staabm commented Dec 6, 2025

I'm not sure why it exits with "code 1"? Having no coverage driver should not be a problem - or should it?

#43

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Unit Tests fail since addToWriter has been added

2 participants