[QUIC] Investigate failing test

[ManickaP]

Related to #121567

[ManickaP]

/azp run runtime-extra-platforms

[azure-pipelines]

Azure Pipelines failed to run 1 pipeline(s).

[dotnet-policy-service]

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

[ManickaP]

/azp list

[azure-pipelines]

CI/CD Pipelines for this repository:

• runtime-coreclr outerloop
• runtime-coreclr jitstress
• runtime-coreclr jitstressregs
• runtime-coreclr jitstress2-jitstressregs
• runtime-coreclr gcstress0x3-gcstress0xc
• runtime-coreclr gcstress-extra
• runtime-coreclr r2r-extra
• runtime-coreclr jitstress-isas-x86
• runtime-coreclr jitstress-isas-arm
• runtime-coreclr jitstressregs-x86
• runtime-coreclr libraries-jitstressregs
• runtime-coreclr libraries-jitstress2-jitstressregs
• runtime-coreclr r2r
• runtime-coreclr runincontext
• runtime-coreclr crossgen2
• runtime-libraries-coreclr outerloop
• runtime-libraries-coreclr outerloop-windows
• runtime-libraries-coreclr outerloop-linux
• runtime-libraries-coreclr outerloop-osx
• runtime
• runtime-libraries enterprise-linux
• runtime-libraries stress-http
• runtime-libraries stress-ssl
• runtime-dev-innerloop
• runtime-coreclr crossgen2 outerloop
• coreclr-release-outerloop-nightly
• runtime-coreclr crossgen2-composite
• runtime-jit-experimental
• runtime-coreclr libraries-jitstress
• dotnet-linker-tests
• runtime-coreclr ilasm
• runtime-coreclr crossgen2-composite gcstress
• runtime-coreclr pgo
• runtime-coreclr libraries-pgo
• Antigen
• runtime-community
• Fuzzlyn
• runtime-coreclr superpmi-replay
• runtime-wasm
• runtime-coreclr superpmi-diffs
• runtime-coreclr superpmi-asmdiffs-checked-release
• runtime-extra-platforms
• jit-cfg
• runtime-wasm-perf
• runtime-llvm
• runtime-coreclr jitstress-random
• runtime-coreclr libraries-jitstress-random
• runtime-wasm-non-libtests
• runtime-android
• runtime-androidemulator
• runtime-ioslike
• runtime-ioslikesimulator
• runtime-linuxbionic
• runtime-maccatalyst
• runtime-coreclr pgostress
• runtime-coreclr jitstress-isas-avx512
• runtime-libraries-mono outerloop
• runtime-sanitized
• runtime-wasm-dbgtests
• runtime-wasm-optional
• runtime-nativeaot-outerloop
• runtime-coreclr superpmi-collect-test
• runtime-diagnostics
• runtime-interpreter
• runtime-report-green
• runtime-coreclr hardware-intrinsics
• runtime-libraries-interpreter
• runtime-libraries stress-http-pr
• runtime-libraries stress-ssl-pr
• hardware-intrinsics-arm64

[ManickaP]

/azp run runtime-coreclr libraries-jitstress

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[Copilot]

Pull request overview

This PR instruments System.Net.Quic functional testing to investigate the intermittent MultipleReadsAndWrites failure linked to issue #121567.

Changes:

• Adds networking event-source logging to MultipleReadsAndWrites.
• Increases the test loop from 100 to 10,000 iterations with a much larger per-iteration timeout.
• Adds timing/disposal changes around the stream write/read flow.

[ManickaP]

/azp run runtime-coreclr libraries-jitstress

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ManickaP]

Problem found, there's a race between RECEIVE event and ReadAsync that manifests with unblocking a 0-byte read when it shouldn't. In this test, it leads to the consuming stream wrongfully thinking it already received FIN and thus Dispose aborting the reading side.
I have a stable repro with Thread.Sleep in HandleEventReceive, closing this PR.