Increase Awaitility timeout to 5s in AbstractAsyncThreadContextTestBase
#3956
+14
−17
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.
I increased the Awaitility wait in
AbstractAsyncThreadContextTestBase
from 500 ms to 5 seconds to avoid a timing flake where the async logger ring buffer was not freed quickly enough on some machines. This is a minimal, test only change that keeps the same assertions but gives more time for slow or busy CI runners, especially on Windows. Five seconds should absorb temporary scheduling or I/O delays while keeping tests fast. We can adjust the timeout or make it configurable later if needed.Fixes #3005.