testing: btlr update #4594
Merged
testing: btlr update #4594
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tmatsuo
reviewed
Aug 28, 2020
| @@ -146,6 +146,7 @@ test_prog="${PROJECT_ROOT}/.kokoro/tests/run_single_test.sh" | |||
|
|
|||
| btlr_args=( | |||
| "run" | |||
| "--max-cmd-duration=30m" | |||
There was a problem hiding this comment.
What happens when it timeouts? I presume the test will fail. Am I right?
There was a problem hiding this comment.
Yes (specifically, it sends a sigterm to the command and which will end the python process and give a non-zero exit code).
The error reported will be "signal: killed" in the summary statement for the cmd.
tmatsuo
approved these changes
Aug 28, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Updates btlr with a version that finishes printing logs upon sigterm signals, and adds a per-command timeout to prevent long jobs from hogging a thread for too long.
Fixes #4104
Fixes #4103