System.IO.Tests.File_ReadWriteAllBytes.ReadAllBytes_NonSeekableFileStream_InWindows failed

[runfoapp]

Runfo Tracking Issue: System.IO.Tests.File_ReadWriteAllBytes.ReadAllBytes_NonSeekableFileStream_InWindows failed

Build	Definition	Kind	Run Name

Build Result Summary

Day Hit Count	Week Hit Count	Month Hit Count
0	0	0

Tagging subscribers to this area: @dotnet/area-system-io
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Runfo Creating Tracking Issue (data being generated)

Author:	runfoapp[bot]
Assignees:	-
Labels:	area-System.IO, untriaged
Milestone:	-

[safern]

I couldn't find an existing issue for this test and just hit it on: #60415

cc: @krwq

[ericstj]

Looks like this test was just added in #58434 and is failing in many PRs. @lateapexearlyspeed @adamsitnik

[lateapexearlyspeed]

Hi @ericstj Sorry about that.
Hi @adamsitnik seems this WaitForConnectionAsync() in test case takes long time sometimes. I just run this test in my local pc to verify that time-consuming call. And eventually it can return back if remove cancellation token source. Current master code cancels cts after waiting for 50 second. Not sure if we should remove cts (like what we did for unix version test.) ?

[ericstj]

No worries, this happens a lot with tests that have open ended timeouts like this. The scale we run dotnet/runtime tests + load on the machine can cause things to take a lot longer than you'd think possible.