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: set error reporting to E_ALL #65

Conversation

jrfnl
Copy link
Collaborator

@jrfnl jrfnl commented Jun 21, 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.

Note: as the CI run isn't failing on the deprecation notice as addressed in #64, this PR exposes a shortage of tests, which should be addressed, though this is outside the scope of this PR.

@jrfnl jrfnl mentioned this pull request Jun 21, 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.
@jrfnl jrfnl force-pushed the feature/ghactions-turn-on-error-reporting branch from 99a636f to 74ab497 Compare August 13, 2021 05:39
@jrfnl
Copy link
Collaborator Author

jrfnl commented Aug 13, 2021

Rebased without changes just to check the current status against PHP 8.1.

@grogy grogy merged commit e80d321 into php-parallel-lint:master Aug 13, 2021
@grogy
Copy link
Member

grogy commented Aug 13, 2021

Thank you, it makes sense

@jrfnl jrfnl deleted the feature/ghactions-turn-on-error-reporting branch August 13, 2021 06:03
@glensc
Copy link

glensc commented Dec 1, 2021

this is attributed as @glensc in changelog:

GH Actions: set error reporting to E_ALL #65 from @glensc.

@grogy
Copy link
Member

grogy commented Dec 1, 2021

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

Successfully merging this pull request may close these issues.

3 participants