Updated bzt_on_pod.sh to run inside tmux sessions to recover from net… #1855
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 in bzt_on_pod.sh so that execution happens inside tmux sessions. Sometimes bzt execution on pod fails because of network errors and script finishes with the error message like that:
"Unhandled Error" err="next reader: websocket: close 1006 (abnormal closure): unexpected EOF"
The idea is to execute bzt in session so that in case of network error script continue running and it's possible to restore connection to the session after the failure.