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

If one CodeChecker store fails, the entire running fails, instead of skipping #50

Open
whisperity opened this issue May 20, 2022 · 0 comments

Comments

@whisperity
Copy link
Contributor

When running the analyses, it is possible that CodeChecker store commands will fail if the size of /tmp (where the server does temporary unpacking of the stored run data) is limited compared to the size of the stored result set (i.e. only 4 GiB instead of the 14 GiB needed). In this case, the run will not appear on the server.

However, the post_process step (after running every configuration for the project) would like to query the run data. In this case, for the failed-to-store run, an empty JSON is returned, which does not have the resultCount key. This exception escapes and tears down the entire analysis, which means that subsequent projects are immediately left unanalysed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant