-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Quarantine StreamPool_MultipleStreamsConcurrent_StreamsReturnedToPool #39477
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I believe we'd like to keep these issues open to ensure the |
Test is failing again, same failure, logs look the exact same as before when it was failing. Failing Test(s)
Error Message
Stacktrace
Logs
Build |
This test hasn't failed in the last 30 days. |
All of the line numbers have moved, but it looks like the failing assert was probably about the stream pool count. |
A stream won't go back into the pool unless it has finished closing gracefully. There's no obvious error in the log, but maybe it was still in the process of shutting down when the assert was evaluated? |
Sleeping for three seconds before returning the stream to the pool doesn't break the test, so that's probably not the race. |
Putting a delay before the stream's status is set does break the test, so there's a race there. Edit: This isn't totally fair since the test uses simulated time, but it certainly seems to indicate that it's not waiting on the stream to complete before checking the pool count. |
Wait for streams to complete before triggering a pool update since they won't be eligible for reuse if they haven't completed. For dotnet#39477
Wait for streams to complete before triggering a pool update since they won't be eligible for reuse if they haven't completed. For #39477
This was un-quarantined by #58368 . |
Failing Test(s)
Error Message
Stacktrace
Logs
Http2ConnectionTests_StreamPool_MultipleStreamsConcurrent_StreamsReturnedToPool.log
Build
https://dev.azure.com/dnceng/public/_build/results?buildId=1549959&view=results
The text was updated successfully, but these errors were encountered: