You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some files in my project take very long to analyse with just clang-tidy (nearly 2 hours for just some 1200 lines of heavy Eigen Linear Algebra), which means they may end up blocking me from working on the reports for another hour or more after the other files are done. In fact, I am currently waiting for two files to finish, 1.5hours after the last ones finished.
Would it be possible to browse reports that already exist in the file system even if a analysis is running? Especially of files which aren't even analysed at the moment (can't browse reports of any file when I am just analysing one).
For future runs I'll just exclude those files (or analyse file-by-file), but when first starting to use codechecker this hinders efficiency quite a lot.
Thank you for your work on this!
The text was updated successfully, but these errors were encountered:
Sadly this is currently impossible due to how CodeChecker stores analysis results. We're planning to rework how these results are stored, but I'm not sure if this feature was considered before.
I created an issue on the CodeChecker repo for it as well: Ericsson/codechecker#4184
Some files in my project take very long to analyse with just clang-tidy (nearly 2 hours for just some 1200 lines of heavy Eigen Linear Algebra), which means they may end up blocking me from working on the reports for another hour or more after the other files are done. In fact, I am currently waiting for two files to finish, 1.5hours after the last ones finished.
Would it be possible to browse reports that already exist in the file system even if a analysis is running? Especially of files which aren't even analysed at the moment (can't browse reports of any file when I am just analysing one).
For future runs I'll just exclude those files (or analyse file-by-file), but when first starting to use codechecker this hinders efficiency quite a lot.
Thank you for your work on this!
The text was updated successfully, but these errors were encountered: