Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
FAIL
actions were being logged at "Error" level, but do not halt patator execution, so they are also moved to stdout.logging.CRITICAL
level will continue to go to stderr to make future development easier.-q
) will suppress non-critical-error output.Rationale
This is partially in response to #60 and partially for my company's own use in automating use of Patator.
The workaround suggested in the linked issue is to pipe stderr to
/dev/null
and use one of the other flags to write to an output file. This does solve the problem, but it also creates the issue of "hiding" critical errors.This change keeps errors visible and makes working with command-line output easier by writing to the dedicated stdout stream.