Skip to content
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

Make reports available to CodeChecker parse incrementally during analysis #4184

Open
Discookie opened this issue Mar 6, 2024 · 0 comments
Open
Labels
analyzer 📈 Related to the analyze commands (analysis driver) CLI 💻 Related to the command-line interface, such as the cmd, store, etc. commands

Comments

@Discookie
Copy link
Contributor

Related issue for the VS Code plugin: Ericsson/CodecheckerVSCodePlugin#143

For local use of CodeChecker, when doing a full CodeChecker analyze run, sometimes a couple files take vastly longer than the rest. Until the full analysis is done, CodeChecker parse has no ability to read partial results.

In general, CodeChecker parse should support reading partial analysis results. This is not a straightforward problem, and would require reworking how metadata is stored, to become atomic.

@whisperity whisperity added CLI 💻 Related to the command-line interface, such as the cmd, store, etc. commands analyzer 📈 Related to the analyze commands (analysis driver) labels Mar 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
analyzer 📈 Related to the analyze commands (analysis driver) CLI 💻 Related to the command-line interface, such as the cmd, store, etc. commands
Projects
None yet
Development

No branches or pull requests

2 participants