-
-
Notifications
You must be signed in to change notification settings - Fork 30.5k
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
Publish C-level coverage of the CPython test suite #94759
Labels
Comments
2 tasks
mdboom
changed the title
Public C-level coverage of the CPython test suite
Publish C-level coverage of the CPython test suite
Jul 11, 2022
tiran
added a commit
to tiran/cpython
that referenced
this issue
Jul 12, 2022
- fixed issue linker flags, LIBS is not passed to BLDSHARED - include version and git commit in output - include "Includes" directory, headers now have inline functions
tiran
added a commit
that referenced
this issue
Jul 13, 2022
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
Jul 13, 2022
(cherry picked from commit f5c02af) Co-authored-by: Christian Heimes <[email protected]>
miss-islington
added a commit
that referenced
this issue
Jul 13, 2022
(cherry picked from commit f5c02af) Co-authored-by: Christian Heimes <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature or enhancement
Automatically publish C-level coverage of the CPython test suite.
Pitch
Recent issues, such as the problems with frame.setlineno, have revealed that the C-level coverage of the test suite isn't perfect. While source-level coverage isn't the only metric of a good test suite, paying closer attention to it should help us have more confidence when making changes to the CPython core.
Proposed design for MVP
make coverage-report
does.python
org for this purpose. This keeps all of the credential management within Github.Out of scope
Creating diffs between coverage runs seems like it would be useful, but I haven't found a good tool for that yet.
Python-level coverage reports would likewise be useful, but should be a follow-on to this.
Previous discussion
@brettcannon had set up coverage reports in the past, but they have been broken for a couple of releases. This aims to be simpler than that approach by using a pure Github stack (not using codecov.io) and would just run nightly, not as part of every pull request.
More recent discussion began here: faster-cpython/ideas#426
The text was updated successfully, but these errors were encountered: