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

code coverage is very slow with Python 3.12 #1347

Open
berquist opened this issue Jan 22, 2024 · 3 comments
Open

code coverage is very slow with Python 3.12 #1347

berquist opened this issue Jan 22, 2024 · 3 comments

Comments

@berquist
Copy link
Member

See #1305 (comment). Let's track everything here. I'll collect concrete numbers again, but I recall test time went from ~6 minutes to 5 hours on unit/regression tests. This wasn't just in CI but also on my personal machine outside of Docker.

cc @Andrew-S-Rosen

@berquist
Copy link
Member Author

For unit tests with -m 'not is_method':

version coverage? time (s)
11.7 no 30.68
11.7 yes 52.31
12.1 no 30.45
12.1 yes 2400 and counting

Tracking issues:

$ coverage --help
Coverage.py, version 7.4.0 with C extension
$ coverage debug sys
-- sys -------------------------------------------------------
               coverage_version: 7.4.0
                coverage_module: /home/eric/.pyenv/versions/miniforge3-4.10.3-10/envs/cclib_312/lib/python3.12/site-packages/coverage/__init__.py
                           core: -none-
                        CTracer: available

@Andrew-S-Rosen
Copy link
Contributor

This is consistent with my testing as well. When I ran aspects of my suite "manually" without using coverage reports or even pytest, the speed seemed okay.

@berquist berquist changed the title cclib is very slow with Python 3.12 code coverage is very slow with Python 3.12 Jan 22, 2024
@berquist
Copy link
Member Author

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

No branches or pull requests

2 participants