Skip to content

Conversation

vkavalenka80
Copy link
Collaborator

@vkavalenka80 vkavalenka80 commented Sep 23, 2025

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.

…work issues.

Updated EBS snapshot for bitbucket 9.4.9 with increased number of threads and events queue in bitbucket.properties
Copy link

Thank you for your submission! Like many open source projects, we ask that you sign our CLA (Contributor License Agreement) before we can accept your contribution.
If your email is listed below, please ensure that you sign the CLA with the same email address.

The following users still need to sign our CLA:
❌vkavalenka80

Already signed the CLA? To re-check, try refreshing the page.

1. Interactive (default one) - tests are running tmux session and user can interact with that
2. Non-interactive (requires --ci command line argument) - tests are still running in tmux session, but user cant interact and only see streamed tmux logs
@vkavalenka80 vkavalenka80 merged commit 4ba8490 into dev Sep 25, 2025
6 checks passed
@vkavalenka80 vkavalenka80 deleted the issue/dev/ECO-963-run-bzt-in-session branch September 25, 2025 09:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants