Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[prerelease] Performance regression?
See original GitHub issueAccording to nikolaizujev on Twitter:
Tested on several internal projects, noticed almost 2x slowdown compared to 6.2.5 on py3.8
Unfortunately no reproducer, but I got .prof dumps from them: Dropbox - pytest - Simplify your life
Opening this to remind myself to have a look at those before the final release - but ideally we’d have a proper reproducer so we can e.g. bisect this. Does anyone have any guess what could be the culprit? I only see a very small slowdown for my own project.
@hroncok Is there perhaps a way to find out which packages in Fedora took significantly longer to run tests with pytest 7 compared to 6? This would mainly be for runs which still pass, because if there are failures, all bets regarding the runtime are off anyways.
Issue Analytics
- State:
- Created 2 years ago
- Comments:32 (32 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I might be able to test that in Fedroa with the git HEAD as well even without rc.
Oh, also, how do folks feel about a quick 7.0.0rc2 now? We still need to take care of #9002 and #9471 (plus potentially “unknown unknowns” from #9415?), but that would mean it’s easy for people (and probably Fedora?) to test the fixes which we have so far (and it makes it easier to ask the original reporter to test this fix too).