Quarantine dotnet-user-secrets InitCommandTests

[halter73]

InitCommandTests caused the latest official build to fail with the following error.

System.InvalidOperationException : Could not load the MSBuild project '/tmp/usersecretstest/a20b03aa-de4a-4b52-8cdb-4fe9cbc456fc/TestProject.csproj'.
at Microsoft.Extensions.SecretManager.Tools.Internal.ProjectIdResolver.Resolve(String project, String configuration) in /_/src/Tools/dotnet-user-secrets/src/Internal/ProjectIdResolver.cs:line 101
at Microsoft.Extensions.SecretManager.Tools.Tests.InitCommandTests.AddsSecretIdToProject() in /_/src/Tools/dotnet-user-secrets/test/InitCommandTest.cs:line 43

@dotnet/aspnet-build

[BrennanConroy]

It was only AddsSecretIdToProject that failed not the whole class.
Also, could you do me a favor and add the exit code to the output?

aspnetcore/src/Tools/dotnet-user-secrets/src/Internal/ProjectIdResolver.cs

Line 99 in 0d15648

_reporter.Verbose(outputBuilder.ToString());

I have a suspicion that this is the same issue we've been seeing with some 139 exit codes.

[halter73]

It was only AddsSecretIdToProject that failed not the whole class.

What would cause AddsSecretIdToProject to fail in this way but not AddsSpecificSecretIdToProject, AddsEscapedSpecificSecretIdToProject, etc.?

I'm tempted to quarantine SecretManagerTests too since it uses the same UserSecretsTestFixture, but I updated the PR to quarantine only the tests that both use the fixture and call ProjectIdResolver.Resolve().

Also, could you do me a favor and add the exit code to the output?

Done.

[BrennanConroy]

What would cause AddsSecretIdToProject to fail in this way but not AddsSpecificSecretIdToProject, AddsEscapedSpecificSecretIdToProject, etc.?

A race in process exiting. Maybe we should just quarantine the whole thing until the issue is fixed in Runtime...

I downloaded the core dump and it looks like the same issue that is being investigated in dotnet/runtime#34231

[Pilchie]

👀