test: fix flaky keepalive timeout test on slow platforms #60664
+4
−3
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.
Fixes: #60656
The test was setting keepAliveTimeout with platformTimeout() but
keepAliveTimeoutBuffer remained at the hardcoded default of 1000ms.
This caused timing issues on slow CI platforms where platformTimeout
scales up timeout values but the buffer did not scale accordingly.
Now both keepAliveTimeout and keepAliveTimeoutBuffer are set using
platformTimeout() to ensure consistent behavior across all platforms