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.

Sign up for GitHub

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

Jump to bottom

parse should fail when path does not exist #4186

Closed
tolikzinovyev opened this issue Mar 9, 2024 · 0 comments · Fixed by #4212
Closed

parse should fail when path does not exist #4186

tolikzinovyev opened this issue Mar 9, 2024 · 0 comments · Fixed by #4212
Labels
CLI 💻 Related to the command-line interface, such as the cmd, store, etc. commands good first issue

Comments

@tolikzinovyev
Copy link

Is your feature request related to a problem? Please describe.
When parse is given a path that doesn't exist, it doesn't output any error. Instead it outputs

----======== Summary ========----
---------------------------------------------
Number of processed analyzer result files | 0
Number of analyzer reports                | 0
---------------------------------------------
----=================----

I was using ./report with analyze and ./reports with parse because of copy-paste and couldn't understand why I'm getting no results for an hour. :(

Describe the solution you would like
parse should print an error and terminate with a non-zero code when the given path does not exist.

Describe alternatives you have considered

Additional context
@vodorok vodorok added good first issue CLI 💻 Related to the command-line interface, such as the cmd, store, etc. commands labels Mar 13, 2024
noraz31 pushed a commit to noraz31/codechecker that referenced this issue Apr 11, 2024
Do not allow parse if the <report dir> does not exist
d2f2b0f 
This change prevents the CodeChecker parse command
from running if the entered report dir or filepath
parameter does not exist.
Up until now, the parse command ran with any parameters,
reporting zero findings if a wrong parameter was entered.
Fixes Ericsson#4186
@noraz31 noraz31 mentioned this issue Apr 11, 2024
Merged
noraz31 pushed a commit to noraz31/codechecker that referenced this issue Apr 25, 2024
Do not allow parse if the <report dir> does not exist
8480c51 
This change prevents the CodeChecker parse command
from running if the entered report dir or filepath
parameter does not exist.
Up until now, the parse command ran with any parameters,
reporting zero findings if a wrong parameter was entered.
Fixes Ericsson#4186
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
CLI 💻 Related to the command-line interface, such as the cmd, store, etc. commands good first issue
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Do not allow parse if the <report dir> does not exist noraz31/codechecker
2 participants
@tolikzinovyev @vodorok