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

TEST PR: Do not merge #10

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

bbatsche
Copy link
Member

@bbatsche bbatsche commented Jan 6, 2021

Testing pull request from separate fork

@bbatsche
Copy link
Member Author

bbatsche commented Jan 6, 2021

Unit & Integration Test Results

✅ All unit and integration tests have passed.

Unit Test Output

> phpunit --configuration tests/unit '--log-junit' 'tests/unit/tmp/junit.xml' '--coverage-clover' 'tests/unit/tmp/clover.xml'
PHPUnit 7.5.20 by Sebastian Bergmann and contributors.

.............................................................   61 / 1454 (  4%)
.............................................................  122 / 1454 (  8%)
.............................................................  183 / 1454 ( 12%)
.............................................................  244 / 1454 ( 16%)
.............................................................  305 / 1454 ( 20%)
.............................................................  366 / 1454 ( 25%)
.............................................................  427 / 1454 ( 29%)
.............................................................  488 / 1454 ( 33%)
.............................................................  549 / 1454 ( 37%)
.............................................................  610 / 1454 ( 41%)
.............................................................  671 / 1454 ( 46%)
.............................................................  732 / 1454 ( 50%)
.............................................................  793 / 1454 ( 54%)
.............................................................  854 / 1454 ( 58%)
.............................................................  915 / 1454 ( 62%)
.............................................................  976 / 1454 ( 67%)
............................................................. 1037 / 1454 ( 71%)
............................................................. 1098 / 1454 ( 75%)
............................................................. 1159 / 1454 ( 79%)
............................................................. 1220 / 1454 ( 83%)
............................................................. 1281 / 1454 ( 88%)
............................................................. 1342 / 1454 ( 92%)
............................................................. 1403 / 1454 ( 96%)
...................................................           1454 / 1454 (100%)

Time: 31.65 seconds, Memory: 78.00 MB

OK (1454 tests, 4586 assertions)

Generating code coverage report in Clover XML format ... done

Integration Test Output

> phpunit --configuration tests/integration '--log-junit' 'tests/integration/tmp/junit.xml'
PHPUnit 7.5.20 by Sebastian Bergmann and contributors.

................................................................. 65 / 65 (100%)


Time: 6.93 seconds, Memory: 28.00 MB

OK (65 tests, 69 assertions)

This comment was generated by Jenkins job ece-tools/unit build 71.

@bbatsche
Copy link
Member Author

bbatsche commented Jan 6, 2021

Static Analysis & Code Style Results

✅ All static analysis and code style checks have passed.

PHP Codesniffer Output

> phpcs src --standard=tests/static/phpcs-ruleset.xml -p -n
............................................................  60 / 689 (9%)
............................................................ 120 / 689 (17%)
............................................................ 180 / 689 (26%)
............................................................ 240 / 689 (35%)
............................................................ 300 / 689 (44%)
............................................................ 360 / 689 (52%)
............................................................ 420 / 689 (61%)
............................................................ 480 / 689 (70%)
............................................................ 540 / 689 (78%)
............................................................ 600 / 689 (87%)
............................................................ 660 / 689 (96%)
.............................                                689 / 689 (100%)


Time: 39.47 secs; Memory: 24MB


PHP Mess Detector Output


Found 0 violations and 0 errors in 22106ms

�[32mNo mess detected�[0m

PHPStan Output

> phpstan analyse -c tests/static/phpstan.neon '--no-progress'

������  You're running a really old version of PHPStan.���

The last release in the 0.11.x series with new features
and bugfixes was released on October 22nd 2019,
that's 442 days ago.

Since then more than 50 new PHPStan versions were released
with hundreds of new features, bugfixes, and other
quality of life improvements.

To learn about what you're missing out on, check out
this blog with articles about the latest major releases:
https://phpstan.org/blog

Historically, the main two blockers preventing
people from upgrading were:
1) Composer conflicts with other dependencies.
2) Errors discovered by the new PHPStan version and no time
   to fix them to get to a green build again.

Today, neither of them is a problem anymore thanks to:
1) phpstan/phpstan package having zero external dependencies.
2) Baseline feature letting you use the latest release
   right away even with pre-existing errors.
   Read more about it here: https://phpstan.org/user-guide/baseline

Upgrade today to PHPStan 0.12 by using
"phpstan/phpstan": "^0.12" in your composer.json.


������  You're running a really old version of PHPStan.���

The last release in the 0.11.x series with new features
and bugfixes was released on October 22nd 2019,
that's 442 days ago.

Since then more than 50 new PHPStan versions were released
with hundreds of new features, bugfixes, and other
quality of life improvements.

To learn about what you're missing out on, check out
this blog with articles about the latest major releases:
https://phpstan.org/blog

Historically, the main two blockers preventing
people from upgrading were:
1) Composer conflicts with other dependencies.
2) Errors discovered by the new PHPStan version and no time
   to fix them to get to a green build again.

Today, neither of them is a problem anymore thanks to:
1) phpstan/phpstan package having zero external dependencies.
2) Baseline feature letting you use the latest release
   right away even with pre-existing errors.
   Read more about it here: https://phpstan.org/user-guide/baseline

Upgrade today to PHPStan 0.12 by using
"phpstan/phpstan": "^0.12" in your composer.json.


 [OK] No errors                                                                 


This comment was generated by Jenkins job ece-tools/static build 69.

@bbatsche
Copy link
Member Author

bbatsche commented Jan 6, 2021

Static Analysis & Code Style Results

✅ All static analysis and code style checks have passed.

PHP Codesniffer Output

> phpcs src --standard=tests/static/phpcs-ruleset.xml -p -n
............................................................  60 / 689 (9%)
............................................................ 120 / 689 (17%)
............................................................ 180 / 689 (26%)
............................................................ 240 / 689 (35%)
............................................................ 300 / 689 (44%)
............................................................ 360 / 689 (52%)
............................................................ 420 / 689 (61%)
............................................................ 480 / 689 (70%)
............................................................ 540 / 689 (78%)
............................................................ 600 / 689 (87%)
............................................................ 660 / 689 (96%)
.............................                                689 / 689 (100%)


Time: 24.39 secs; Memory: 24MB


PHP Mess Detector Output


Found 0 violations and 0 errors in 16300ms

�[32mNo mess detected�[0m

PHPStan Output

> phpstan analyse -c tests/static/phpstan.neon '--no-progress'

������  You're running a really old version of PHPStan.���

The last release in the 0.11.x series with new features
and bugfixes was released on October 22nd 2019,
that's 442 days ago.

Since then more than 50 new PHPStan versions were released
with hundreds of new features, bugfixes, and other
quality of life improvements.

To learn about what you're missing out on, check out
this blog with articles about the latest major releases:
https://phpstan.org/blog

Historically, the main two blockers preventing
people from upgrading were:
1) Composer conflicts with other dependencies.
2) Errors discovered by the new PHPStan version and no time
   to fix them to get to a green build again.

Today, neither of them is a problem anymore thanks to:
1) phpstan/phpstan package having zero external dependencies.
2) Baseline feature letting you use the latest release
   right away even with pre-existing errors.
   Read more about it here: https://phpstan.org/user-guide/baseline

Upgrade today to PHPStan 0.12 by using
"phpstan/phpstan": "^0.12" in your composer.json.


������  You're running a really old version of PHPStan.���

The last release in the 0.11.x series with new features
and bugfixes was released on October 22nd 2019,
that's 442 days ago.

Since then more than 50 new PHPStan versions were released
with hundreds of new features, bugfixes, and other
quality of life improvements.

To learn about what you're missing out on, check out
this blog with articles about the latest major releases:
https://phpstan.org/blog

Historically, the main two blockers preventing
people from upgrading were:
1) Composer conflicts with other dependencies.
2) Errors discovered by the new PHPStan version and no time
   to fix them to get to a green build again.

Today, neither of them is a problem anymore thanks to:
1) phpstan/phpstan package having zero external dependencies.
2) Baseline feature letting you use the latest release
   right away even with pre-existing errors.
   Read more about it here: https://phpstan.org/user-guide/baseline

Upgrade today to PHPStan 0.12 by using
"phpstan/phpstan": "^0.12" in your composer.json.


 [OK] No errors                                                                 


This comment was generated by Jenkins job ece-tools/static build 70.

@bbatsche
Copy link
Member Author

bbatsche commented Jan 6, 2021

Unit & Integration Test Results

✅ All unit and integration tests have passed.

Unit Test Output

> phpunit --configuration tests/unit '--log-junit' 'tests/unit/tmp/junit.xml' '--coverage-clover' 'tests/unit/tmp/clover.xml'
PHPUnit 7.5.20 by Sebastian Bergmann and contributors.

.............................................................   61 / 1454 (  4%)
.............................................................  122 / 1454 (  8%)
.............................................................  183 / 1454 ( 12%)
.............................................................  244 / 1454 ( 16%)
.............................................................  305 / 1454 ( 20%)
.............................................................  366 / 1454 ( 25%)
.............................................................  427 / 1454 ( 29%)
.............................................................  488 / 1454 ( 33%)
.............................................................  549 / 1454 ( 37%)
.............................................................  610 / 1454 ( 41%)
.............................................................  671 / 1454 ( 46%)
.............................................................  732 / 1454 ( 50%)
.............................................................  793 / 1454 ( 54%)
.............................................................  854 / 1454 ( 58%)
.............................................................  915 / 1454 ( 62%)
.............................................................  976 / 1454 ( 67%)
............................................................. 1037 / 1454 ( 71%)
............................................................. 1098 / 1454 ( 75%)
............................................................. 1159 / 1454 ( 79%)
............................................................. 1220 / 1454 ( 83%)
............................................................. 1281 / 1454 ( 88%)
............................................................. 1342 / 1454 ( 92%)
............................................................. 1403 / 1454 ( 96%)
...................................................           1454 / 1454 (100%)

Time: 20.2 seconds, Memory: 78.00 MB

OK (1454 tests, 4586 assertions)

Generating code coverage report in Clover XML format ... done

Integration Test Output

> phpunit --configuration tests/integration '--log-junit' 'tests/integration/tmp/junit.xml'
PHPUnit 7.5.20 by Sebastian Bergmann and contributors.

................................................................. 65 / 65 (100%)


Time: 4.06 seconds, Memory: 28.00 MB

OK (65 tests, 69 assertions)

This comment was generated by Jenkins job ece-tools/unit build 72.

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.

1 participant