System.Runtime.InteropServices.Tests causing OSX queue backup from uploading dump

[elinor-fung]

See https://github.com/dotnet/core-eng/issues/15520#issuecomment-1032835597

Going to temporarily disable coredumps for libraries tests on macOS while we investigate more, since this is causing issues for everyone using the queue.

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

Issue Details

---

See https://github.com/dotnet/core-eng/issues/15520#issuecomment-1032835597

Going to temporarily disable coredumps for libraries tests on macOS while we investigate more, since this is causing issues for everyone using the queue.

Author:	elinor-fung
Assignees:	-
Labels:	area-System.Runtime.InteropServices
Milestone:	-

[agocke]

Thanks! If this is a reliable repro I could try running it locally.

[elinor-fung]

That would be great. My theory is that we have at least one expected dump from PosixSignalRegistrationTests.SignalCanCancelTermination for SIGQUIT and not cancelling termination:

runtime/src/libraries/System.Runtime.InteropServices/tests/System.Runtime.InteropServices.UnitTests/System/Runtime/InteropServices/PosixSignalRegistrationTests.Unix.cs

Lines 168 to 169 in b201a16

	[InlineData(PosixSignal.SIGQUIT, false, 131)]
	public void SignalCanCancelTermination(PosixSignal signal, bool cancel, int expectedExitCode)

If it is that, it should be consistent.

Many of the dumps I see are coming from passed tests. I know @stephentoub had mentioned/reported needing a way to avoid uploading dumps for expected crashes, but I can't seem to find the issue.

WorkItems
| where FriendlyName == "System.Runtime.InteropServices.Tests" and QueueName == "osx.1200.amd64.open" and Queued >= ago(1d)
| join Files on WorkItemId
| where FileName startswith "core"
| project Queued, Status, ExitCode, QueueName, ConsoleUri, SizeBytesLong

[stephentoub]

Many of the dumps I see are coming from passed tests. I know @stephentoub had mentioned/reported needing a way to avoid uploading dumps for expected crashes, but I can't seem to find the issue.

https://github.com/dotnet/core-eng/issues/15333

[AaronRobinsonMSFT]

@elinor-fung Was this resolved with https://github.com/dotnet/core-eng/issues/15333?

[elinor-fung]

The immediate issues this was tracking have been addressed/mitigated. The long-term fix is tracked by #65422.