-
Notifications
You must be signed in to change notification settings - Fork 48
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
Stuck in: "analysis I π starting file result creation in cpp check", bombs after 5 hours when the output directory is unavailable #38
Comments
Actually I was impatient: 2023-02-21 21:27:40 analysis I β
scanning complete but at the end it fell over. |
It seems the reason for my slow analysis is because I attempted to analyse a build rather than just source code. 2023-02-21 22:44:49 analysis I β
created the filesystem graph |
I now face another issue: 2023-02-21 23:28:37 analysis I π starting code metric calculation for analysis cpp check
but pygraphviz is already installed:
|
@bruce-optibrium Thank you for your feedback. Emerge does provide the option the activate debug logging in the config file, this could help to identify possible issues or better track progress. You could also use some logging command line args e.g. ( Your idea "It would be better to check for existence of the directory at the start of the analysis instead!" is great, will plan and include this in an upcoming fix/release π. Not quite sure why the import of graphviz fails in windows. Can you try to remove the
as a workaround, to check if the analysis will run without generating the graphviz output? Maybe try to run it first on a smaller codebase or simple on a subdirectory to reduce running time for this first check? Hope this will help you. |
Describe the bug
Analysis is taking a long time with no indication of progress.
emerge -a CPP
edited paths in cpp-template.yml
Describe your environment
emerge-viz installed using pip
The code base is on the medium to large side (14055 fliles of which 7674 are headers, 65440 lines).
I should probably have tried emerge out on something smaller first
and read the manual to see if there are any slow analysis steps worth switching off on a first pass.
The text was updated successfully, but these errors were encountered: