-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[do not merge] Demo incorrect phpunit status (phpunit 6) #34865
Conversation
Codecov Report
@@ Coverage Diff @@
## master #34865 +/- ##
=============================================
- Coverage 65.35% 48.39% -16.96%
=============================================
Files 1208 109 -1099
Lines 69969 10493 -59476
Branches 1280 1280
=============================================
- Hits 45726 5078 -40648
+ Misses 23871 5043 -18828
Partials 372 372
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #34865 +/- ##
=============================================
- Coverage 65.35% 48.39% -16.96%
=============================================
Files 1208 109 -1099
Lines 69969 10493 -59476
Branches 1280 1280
=============================================
- Hits 45727 5078 -40649
+ Misses 23870 5043 -18827
Partials 372 372
Continue to review full report at Codecov.
|
91b59d0
to
1767841
Compare
1767841
to
3f92b1f
Compare
Sadly issue #34858 is not solved by PHPUnit6. |
Sadly, we get the same outcome with PHPUnit6:
https://drone.owncloud.com/owncloud/core/16424/199
runs 9609 unit tests with sqlite and PHP7.1 - it correctly sees 6 failures and exits with error - good.
https://drone.owncloud.com/owncloud/core/16424/207
runs 9609 unit tests with sqlite and PHP7.2 - it correctly sees 6 failures but exits with success status - bad.
https://drone.owncloud.com/owncloud/core/16424/224
runs 9609 unit tests with sqlite and PHP7.3 - it correctly sees 6 failures but exits with success status - bad.
This is the same observed behavior as with PHPUnit5 :(
We need to bump up to PHPUnit6 anyway, but I was also hoping that it would resolve this "exit status" issue.