-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
[workflow] Use gcc matcher to make warnings prominent #18567
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
Conversation
Codecov Report
@@ Coverage Diff @@
## master #18567 +/- ##
==========================================
- Coverage 82.15% 82.06% -0.09%
==========================================
Files 1958 1955 -3
Lines 589837 584012 -5825
Branches 44458 44458
==========================================
- Hits 484560 479289 -5271
+ Misses 95636 95101 -535
+ Partials 9641 9622 -19
Continue to review full report at Codecov.
|
(closing and re-opening to re-run CI) |
Ping @pablogsal @zware Looks like there's no |
Thanks for working on this @ammaraskar :) 🎉 |
This makes warnings and errors from the compiler very prominent so this should help prevent warnings from sneaking into the code base and catch them in review. See https://discuss.python.org/t/using-github-problem-matchers-to-catch-warnings-early/4254 for more details You can see a demo of this in action here: https://github.com/ammaraskar/cpython/pull/15/files#diff-9ba2eeca0f254ece0a9df4d7cb68e870 GCC and Sphinx matchers have previously been added in GH-18567 and GH-20325, respectively.
…H-18532) This makes warnings and errors from the compiler very prominent so this should help prevent warnings from sneaking into the code base and catch them in review. See https://discuss.python.org/t/using-github-problem-matchers-to-catch-warnings-early/4254 for more details You can see a demo of this in action here: https://github.com/ammaraskar/cpython/pull/15/files#diff-9ba2eeca0f254ece0a9df4d7cb68e870 GCC and Sphinx matchers have previously been added in pythonGH-18567 and pythonGH-20325, respectively.
This makes warnings and errors from the compiler very prominent so this should help prevent warnings from sneaking into the code base and catch them in review.
You can see a demo of this in action here: https://github.com/ammaraskar/cpython/pull/16/files#diff-4d35cf8992b795c5e97e9c8b6167cb34
or in screenshot form:
(This PR is sort of a mirror to #18532 but for the linux builds.)