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
Speed up pypy builder, which is slow due to coverage.py #834
Comments
coverage.py 7.3.3 seems to take infinite amounts of time on PyPy for me, even slower than current CI using 4.3.1. Will try other versions. |
Pretty much every version I've tried is ludicrously slow on my computer, weirdly much slower than CI, so it's difficult for me to see if upgrading helps... Another alternative is to skip collecting coverage on PyPy, which will speed it up a lot! |
I'm currently doing some tests with different coverage versions, will post my observations here |
With version
With current version (
On my local machine |
If it's slow enough to be an impediment then this feels like a reasonable solution. |
Your numbers are quite different than mine, mine just runs for 10+ minutes before I just give up and kill it. No idea what's different :( |
As reference in CI it currently takes 10 minutes, vs 2 minutes for everything else. Given @4383's numbers it seems like upgrading to 7.3.3 should help, but maybe not enough. |
Regardless, I probably need this for #638 so will upgrade in the branch for that. |
#836 upgrades to 7.3.3 and there's no meaningful impact on runtime. There's only one tiny bit of code that checks for PyPy, and I bet it could just be made unconditional, in which case coverage on pypy can be dropped. |
I agree with that |
Options:
The text was updated successfully, but these errors were encountered: