Daiki AMINAKA

msquicplatform as well. msquiccoretest works. This means that there seems issue on platform layer 

By shortening the Watchdog to Timeout/2 can avoid the "Aborted". https://github.com/microsoft/msquic/blob/55830d38c86e493711bc4c5fe441de7c13c40dc0/src/test/bin/quic_gtest.cpp#L47 `msquicplatformtest` passed with one error (`TlsTest.HandshakeCertFromFile`) with this change, but msquictest seems having more issues. @nibanks Do we really...

I did not notice the document. but what I did was more simpler than the one written. ```sh perf record -F XX -a -g -o out.perf.data MY_COMMAND perf script -i...

Same src dst port? Just my guess

hmm, nothing other than these. the Loading dialogue quickly disappears and Diagnostic Console shows the error. I feel this is 50% probability Or maybe 100% failed at first, then second...

Is it PerfView side or Extension side?

```pwsh while (1) { wpr.exe -start .\src\manifest\MsQuic.wprp!Full.Light -filemode .\artifacts\bin\windows\x64_Debug_schannel\msquictest.exe --gtest_filter="Basic/WithFamilyArgs.LocalPathChanges*" $Result = $? wpr.exe -stop .\quic.etl if ($Result -eq $false) { Write-Host "BREAK" break } } netsh.exe trace convert .\quic.etl...

Test works without issue once it failed by the issue (or failed by different issue). configuration matter?

[Success.log](https://github.com/microsoft/msquic/files/10830370/Success.log) [Fail.log](https://github.com/microsoft/msquic/files/10830371/Fail.log)

`Server->ForceKeyUpdate()` failed by QUIC_STATUS_INVALID_STATE Then second `Client->ForceKeyUpdate()` continue failing by QUIC_STATUS_INVALID_STATE Trying to repro to know which connection condition matches