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

GH Actions: turn display_errors on #265

Merged
merged 1 commit into from
Jun 22, 2021

Conversation

jrfnl
Copy link
Contributor

@jrfnl jrfnl commented Jun 22, 2021

Turns out the default setting for error_reporting used by the SetupPHP action is error_reporting=E_ALL & ~E_DEPRECATED & ~E_STRICT and display_errors is set to Off.

For the purposes of CI, I'd recommend running with E_ALL and display_errors=On to ensure all PHP notices are shown.

In the test script, error_reporting was already enabled, but the error display was not yet fixed. Sorted now.
In the lint script, both were missing.

Turns out the default setting for `error_reporting` used by the SetupPHP action is `error_reporting=E_ALL & ~E_DEPRECATED & ~E_STRICT` and `display_errors` is set to `Off`.

For the purposes of CI, I'd recommend running with `E_ALL` and `display_errors=On` to ensure **all** PHP notices are shown.

In the `test` script, error_reporting was already enabled, but the error display was not yet fixed. Sorted now.
In the `lint` script, both were missing.
@jrfnl jrfnl added this to the 0.2.x/0.3.0 Next milestone Jun 22, 2021
@jrfnl
Copy link
Contributor Author

jrfnl commented Jun 22, 2021

Note: the current build failure against PHP 8.1 was expected - this is an upstream issue with the PHP Parallel Lint package and I've already pulled a fix there: php-parallel-lint/PHP-Parallel-Lint#64

@dingo-d dingo-d merged commit 15684d0 into develop Jun 22, 2021
@dingo-d dingo-d deleted the feature/ghactions-turn-on-error-reporting branch June 22, 2021 06:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants