Unhandled exception. System.IO.EndOfStreamException: Unable to read beyond the end of the stream.

[Evangelink]

Description

We are trying to enable macos pipeline for our new testing platform and we are getting quite a lot of our acceptance tests related to dump creation failing. See microsoft/testfx#4155

One of the issue is:

Unhandled exception. System.IO.EndOfStreamException: Unable to read beyond the end of the stream.
   at System.IO.BinaryReader.ReadUInt16()
   at Microsoft.Diagnostics.NETCore.Client.IpcHeader.Parse(BinaryReader reader)
   at Microsoft.Diagnostics.NETCore.Client.IpcMessage.Parse(Stream stream)
   at Microsoft.Diagnostics.NETCore.Client.IpcClient.Read(Stream stream)
   at Microsoft.Diagnostics.NETCore.Client.IpcClient.SendMessageGetContinuation(IpcEndpoint endpoint, IpcMessage message)
   at Microsoft.Diagnostics.NETCore.Client.IpcClient.SendMessage(IpcEndpoint endpoint, IpcMessage message)
   at Microsoft.Diagnostics.NETCore.Client.DiagnosticsClient.WriteDump(DumpType dumpType, String dumpPath, WriteDumpFlags flags)
   at Microsoft.Diagnostics.NETCore.Client.DiagnosticsClient.WriteDump(DumpType dumpType, String dumpPath, Boolean logDumpGeneration)
   at Microsoft.Testing.Extensions.Diagnostics.HangDumpProcessLifetimeHandler.TakeDumpAsync() in /_/src/Platform/Microsoft.Testing.Extensions.HangDump/HangDumpProcessLifetimeHandler.cs:line 375
   at Microsoft.Testing.Extensions.Diagnostics.HangDumpProcessLifetimeHandler.ActivityTimerAsync() in /_/src/Platform/Microsoft.Testing.Extensions.HangDump/HangDumpProcessLifetimeHandler.cs:line 318
   at Microsoft.Testing.Platform.Helpers.SystemTask.<>c__DisplayClass4_0.<RunLongRunning>b__0() in /_/src/Platform/Microsoft.Testing.Platform/Helpers/System/SystemTask.cs:line 33
   at System.Threading.Thread.StartCallback()
Test suite failed with and exit code different that 2 (failed tests). Failure related to an unexpected condition. Exit code '134'

Configuration

We are using macos-latest on AzDO hosted pool.

Regression?

No idea, we are enabling macos.
We recently bumped to 0.2.553101, I'll try to downgrade and see if that changes anything.

[tommcdon]

@mikem8361

[Evangelink]

Downgrading didn't help