-
Notifications
You must be signed in to change notification settings - Fork 3
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
check-lint hides errors from all but last run #11
Labels
bug
Something isn't working
Comments
clebergnu
changed the title
check-lint hides errors from all but last runs
check-lint hides errors from all but last run
Oct 2, 2024
harvey0100
added a commit
to harvey0100/avocado-static-checks
that referenced
this issue
Oct 4, 2024
Corrected error handling, check-lint now displays correct exit codes on exit instead of only displaying the last executed commands exit code, keeps track of all failures and displays correct exit code if any failures were present. Reference: avocado-framework#11 Signed-off-by: Harvey Lynden <hlynden@redhat.com>
Merged
harvey0100
added a commit
to harvey0100/avocado-static-checks
that referenced
this issue
Oct 4, 2024
Corrected error handling, check-lint now displays correct exit codes on exit instead of only displaying the last executed commands exit code, keeps track of all failures and displays correct exit code if any failures were present. Reference: avocado-framework#11 Signed-off-by: Harvey Lynden <hlynden@redhat.com>
harvey0100
added a commit
to harvey0100/avocado-static-checks
that referenced
this issue
Oct 10, 2024
Corrected error handling, check-lint now displays correct exit codes on exit instead of only displaying the last executed commands exit code, keeps track of all failures and displays correct exit code if any failures were present. Reference: avocado-framework#11 Signed-off-by: Harvey Lynden <hlynden@redhat.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Because
check-lint
implements the execution ofpylint
on possibly multiple different files (controlled by theavocado-static-checks.conf
file), it needs to keep track of all failures.Currently, the exit code of the script is simply the exit code of the last command executed.
The text was updated successfully, but these errors were encountered: