-
Notifications
You must be signed in to change notification settings - Fork 56
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
The php72 test-report job is always successful #209
Comments
It does look weird… can you try doing an obvious mistake in one of your PRs and see if it is caught by that job? |
Not sure exactly what you call "obvious".. check this PR where I'm adding a new sniff and many files of this repo do not comply with it. Right from the first job you'll notice the PHP 72 that is successful. |
Link for the lazy: https://github.com/doctrine/coding-standard/pull/206/checks?check_run_id=791333879 I think the issue would have to do with this line: Line 9 in 87308f5
I think it is equivalent to vendor/bin/phpcs `find tests/input/* | sort` --report=summary --report-file=phpcs.log
diff -u tests/expected_report.txt phpcs.log
if [ $$? -ne 0 ] && [ $(PHP_74_OR_NEWER) -eq 1 ]
then
git apply -R tests/php-compatibility.patch
exit 1
fi This does not make much sense… maybe it should really be vendor/bin/phpcs `find tests/input/* | sort` --report=summary --report-file=phpcs.log
diff -u tests/expected_report.txt phpcs.log
if [ $(PHP_74_OR_NEWER) -eq 1 ]
then
git apply -R tests/php-compatibility.patch
fi
if [ $$? -ne 0 ]
then
exit 1
fi It was introduced as such in f9d89e0 as part of #144 @lcobucci can you please advise? |
@gmponos thanks for reporting this issue 👍 |
Is this correct?
https://github.com/doctrine/coding-standard/pull/205/checks?check_run_id=788441821
As you can see on this job there are differences but the job is success.
Is this addressed here? https://github.com/doctrine/coding-standard/issues
The text was updated successfully, but these errors were encountered: