NAS-129758 / 24.10 / Try to use persistent connection for CI tests #13935
Conversation
This file contains 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
anodos325
force-pushed
the
add-persistent-ws-connection
branch
2 times, most recently
from
f88126d to
3086d53
Compare
Store a persistent websocket client connection in the truenas_server object we allocate for test runs, and use this for general case where test simply uses `call` test utility. This is to avoid potentially running into issues with rate-limiting on auth endpoints.
anodos325
force-pushed
the
add-persistent-ws-connection
branch
from
a514b92 to
9b7cae1
Compare
bugclerk
changed the title
yocalebo
approved these changes
Jun 26, 2024
|
This PR has been merged and conversations have been locked. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Store a persistent websocket client connection in the truenas_server object we allocate for test runs, and use this for general case where test simply uses
calltest utility. This is to avoid potentially running into issues with rate-limiting on auth endpoints.