[release/5.0-rc2] Restore exception compatibility in TcpListener.EndAccept***#41938
Conversation
|
CI failures seem to be Helix issues (failing to proceed after successful test run). None of them seemt obe related to |
|
Tagging subscribers to this area: @dotnet/ncl |
| IAsyncResult iar = listener.BeginAcceptSocket(callback: null, state: null); | ||
|
|
||
| // Give some time for the underlying OS operation to start: | ||
| Thread.Sleep(50); |
There was a problem hiding this comment.
We often see tests fail because of slow test machines, I wonder whether this will reliably be long enough.
There was a problem hiding this comment.
In this test the next call should throw ObjectDisposedException independently from timing, so slow machines should not bring an issue hopefully.
|
@antonfirsov OK to merge when green. |
|
@dotnet/dnceng it seems Helix had some issues while running some of these legs. Eg., |
|
I clicked rerun failed jobs. |
Sounds like fairly typical network flakiness but taking a peek |
Backport of #41745 to release/5.0-rc2
/cc @antonfirsov
Customer Impact
Removes an unwanted breaking change (#41585), improving migration experience for for users of
TcpListener.This was discovered during app-compat testing.
Testing
A (previously missing) test has been introduced for the case.
Risk
Low or none. The change is limited to the APM methods of
TcpListener.