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
Report generation is taking more time > 30 minutes #58
Comments
Hi! Maybe we could produce a version with a debugging option that would give feedback on the progress, so we could know which part of the code causes the issue. PS: Sorry for the delay, I'm currently traveling... |
Thanks @marcandre I have attached the trace for your reference I tried multiple times, but the following are the stack trace which ends up taking a long time. Also attached as txt file
|
Thank you for the stacktrace. It doesn't look like there's anything strange going on. I did some testing on FWIW, If you look at the timestamps of |
It didn't struct in any file but file generation is slow about 6-7 files per minutes. Will dig further in my free time. |
No idea if that could be an issue, but could you take a look at your memory usage while its running? If you were to get into swap for some reason, that would explain this very slow throughput. |
I have a reproductible case with #68, I will be looking into this asap. |
Updating to the latest |
using
builtin_takeover
and codecov. Codecov report was fast as before, but we wanted to have branch coverage so randeep-cover report
. But unfortunately it is taking more than 30 minutes and still not completed.We had
1.3K files in total. 90K relevant lines
Is there any way to speed it up.
The text was updated successfully, but these errors were encountered: