-
Notifications
You must be signed in to change notification settings - Fork 456
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
async utils: aio_run_command(): check returncode #1181
async utils: aio_run_command(): check returncode #1181
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1181 +/- ##
==========================================
- Coverage 79.81% 77.47% -2.34%
==========================================
Files 216 217 +1
Lines 4141 4169 +28
Branches 515 517 +2
==========================================
- Hits 3305 3230 -75
- Misses 705 798 +93
- Partials 131 141 +10
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't we need to add the new test file to the CI?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup, looks like we need to add the new test file to CI so the coverage will actually update correctly. Otherwise looks good to go, though.
5a8ea14
to
b9bf983
Compare
Raise subprocess.CalledProcessError if subprocess fails with a non-zero return code. Fixes: intel#1177 Signed-off-by: John Andersen <johnandersenpdx@gmail.com>
Changes in intel#1181 to check return codes made it so failed extractions caused cve-bin-tool to halt rather than log an error. This was particularly a problem for .exe files, which we try to extract as zipfiles in case they are self-extracting exectables. Signed-off-by: Terri Oda <terri.oda@intel.com>
Changes in intel#1181 to check return codes made it so failed extractions caused cve-bin-tool to halt rather than log an error. This was particularly a problem for .exe files, which we try to extract as zipfiles in case they are self-extracting exectables. Signed-off-by: Terri Oda <terri.oda@intel.com>
Changes in intel#1181 to check return codes made it so failed extractions caused cve-bin-tool to halt rather than log an error. This was particularly a problem for .exe files, which we try to extract as zipfiles in case they are self-extracting exectables. Signed-off-by: Terri Oda <terri.oda@intel.com>
* fixes #1281 * Related to #1181 Changes in #1181 to check return codes made it so that cve-bin-tool failed if any file did not extract correctly. This changes the default so that failures during extraction are logged but do not halt the scan. Error messages are not logged when the file extension is .exe because users found those confusing (cve-bin-tool tries to unzip all .exe files in case they are self-extracting zipfiles, but many are not) Signed-off-by: Terri Oda <terri.oda@intel.com>
* fixes #1281 * Related to #1181 Changes in #1181 to check return codes made it so that cve-bin-tool failed if any file did not extract correctly. This changes the default so that failures during extraction are logged but do not halt the scan. Error messages are not logged when the file extension is .exe because users found those confusing (cve-bin-tool tries to unzip all .exe files in case they are self-extracting zipfiles, but many are not) Signed-off-by: Terri Oda <terri.oda@intel.com>
No description provided.