-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
System.IO.Pipes.Tests.NamedPipeTest_ServerInOut_ClientInOut_Synchronous.ClonedServer_ActsAsOriginalServer test hang #72608
Comments
Tagging subscribers to this area: @dotnet/area-system-io Issue DetailsHit in #72573: https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-72573-merge-95ae7524d1c140d087/System.IO.Pipes.Tests/1/console.139c5f5b.log?helixlogtype=result
|
cc @stephentoub Potential regression introduced by #72503 . We have not seen hang like this before. |
Duplicate of #72585. I don't believe it's a product regression, but rather this is a new configuration for this particular test (it previously never ran on two InOut named pipes opened for synchronous I/O). I'd opened #72526 for another variation of this, but it appears to be wider spread with this configuration. I'm going to remove the configuration entirely until we can figure it out (and double check that it still hangs prior to my changes, as was the case with the other cited test). |
Hit in #72573: https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-72573-merge-95ae7524d1c140d087/System.IO.Pipes.Tests/1/console.139c5f5b.log?helixlogtype=result
The text was updated successfully, but these errors were encountered: