Skip to content

Conversation

furtib
Copy link

@furtib furtib commented Sep 23, 2025

Why:
When working on Bezel, we encounter a situation where the result files are placed into a read-only folder. By default, CodeChecker store creates a temporary directory for zipping the results before sending them to the server. This directory cannot be created in a read-only folder, causing CodeChecker to crash.

What:
This pull request adds an extra command-line argument, --temp_dir, to the CodeChecker store command, which specifies where temporary files should be created. When this argument is not set, it continues to use the previous implementation.

@furtib furtib requested a review from Szelethus September 23, 2025 15:02
@furtib furtib self-assigned this Sep 23, 2025
@furtib furtib added the bazel 🧩 Directly or inderectly related to bazel support label Sep 23, 2025
Copy link
Contributor

@Szelethus Szelethus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CI is breaking.

Copy link
Contributor

@Szelethus Szelethus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM with a nit.

Comment on lines 279 to 284
help="Specify a path to use as temporary folder. "
"Necessary to have a place to compress files before "
"uploading them. Defaults to the result directory. "
"Normally it isn't necessary to specify. "
"Useful when the folder containing the result folder "
"is read only.")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Specify the location to write the compressed file used for storage. Useful if the results directory is read only. Defaults to the results directory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bazel 🧩 Directly or inderectly related to bazel support
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants