Tomas Weinfurt

I think we should disable the tests on affected platforms. I don't know why the UDS would not be connected. The second link make sense only when `Socket` is created...

It is possible this has same root cause as https://github.com/dotnet/runtime/issues/73621 and https://github.com/dotnet/runtime/issues/69125 and fixed by #73972. While the stack trace may not be the same all bets are off when...

I'm not sure. I was looking at similar issue recently and specially on PRs the failures are often unrelated. Simply putting all "BadExist" together is not sufficient IMHO. It would...

Similar for me. We had ARM64 pipeline for a while on msquic and if was failing occasionally on msbuild. Running tests seems to be ok.

did we reached conciliation if new bistro is needed @omajid @richlander ? As minimum we should rebuild other json files besides runtimeGroups.props and include this with the PR. (dotnet pack...

> Ideally, we would not and this RID could be added via source-build per #50818. Would that mean that RH binaries would be unusable e.g. the RID would work only...

cc: @tmds seems like we do closing magic on invalid socket ... (stack bellow is copy from @danmoseley post) ``` top of stack looks like #10 0x00007f4c7b4ab5cd in ToFileDescriptor (fd=-1)...

Aside from some authentication changes, #70046 would be biggest suspect. It may not be root cause as the assert is in Sockets. I tried to reproduce it (main on Linux)...

BadExit may be misleading in queries... This is not event PR but `main` https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-ececf5ef6b4c4ff2a6/System.Net.Mail.Functional.Tests/1/console.8759b633.log?helixlogtype=result ``` ----- start Thu Aug 25 12:40:46 UTC 2022 =============== To repro directly: ===================================================== pushd ....

ok. I updated my query. My original one was based on the `runfo` issues. So far so good.