Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avoid BuildHost crash in Mono due to missing types #74392

Closed
wants to merge 1 commit into from

Avoid BuildHost crash in Mono due to missing types

3bcf996
Select commit
Loading
Failed to load commit list.
Closed

Avoid BuildHost crash in Mono due to missing types #74392

Avoid BuildHost crash in Mono due to missing types
3bcf996
Select commit
Loading
Failed to load commit list.
Azure Pipelines / roslyn-CI succeeded Sep 5, 2024 in 34m 37s

Build #20240904.14 had test failures

Details

Tests

  • Failed: 8 (0.00%)
  • Passed: 1,214,542 (98.82%)
  • Other: 14,511 (1.18%)
  • Total: 1,229,061

Annotations

Check failure on line 109 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / roslyn-CI

Build log #L109

The process cannot access the file 'D:\a\_work\1\s\artifacts\log\Release\Build.Server.log' because it is being used by another process.

Check failure on line 1 in Microsoft.CodeAnalysis.Editor.UnitTests.RenameTracking.RenameTrackingTaggerProviderTests.RenameTracking_UnmanagedConstraint_Type

See this annotation in the file changed.

@azure-pipelines azure-pipelines / roslyn-CI

Microsoft.CodeAnalysis.Editor.UnitTests.RenameTracking.RenameTrackingTaggerProviderTests.RenameTracking_UnmanagedConstraint_Type

Assert.Equal() Failure
Expected: 1
Actual:   0
Raw output
   at Microsoft.CodeAnalysis.Editor.UnitTests.RenameTracking.RenameTrackingTestState.<AssertTag>d__27.MoveNext() in /_/src/EditorFeatures/Test/RenameTracking/RenameTrackingTestState.cs:line 186
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.CodeAnalysis.Editor.UnitTests.RenameTracking.RenameTrackingTaggerProviderTests.<RenameTracking_UnmanagedConstraint_Type>d__75.MoveNext() in /_/src/EditorFeatures/Test/RenameTracking/RenameTrackingTaggerProviderTests.cs:line 1428
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

Check failure on line 1 in Microsoft.CodeAnalysis.CSharp.Scripting.UnitTests.InteractiveSessionTests.StaticMethodCannotAccessGlobalInstance

See this annotation in the file changed.

@azure-pipelines azure-pipelines / roslyn-CI

Microsoft.CodeAnalysis.CSharp.Scripting.UnitTests.InteractiveSessionTests.StaticMethodCannotAccessGlobalInstance

Unexpected exception: System.OutOfMemoryException: Insufficient memory to continue the execution of the program.
   at System.Runtime.InteropServices.Marshal.AllocHGlobal(IntPtr cb)
   at System.Reflection.Internal.NativeHeapMemoryBlock.DisposableData..ctor(Int32 size)
   at System.Reflection.Internal.StreamMemoryBlockProvider.ReadMemoryBlockNoLock(Stream stream, Int64 start, Int32 size)
   at System.Reflection.PortableExecutable.PEReader..ctor(Stream peStream, PEStreamOptions options, Int32 size)
   at Microsoft.CodeAnalysis.ModuleMetadata.CreateFromStream(Stream peStream, PEStreamOptions options) in /_/src/Compilers/Core/Portable/MetadataReference/ModuleMetadata.cs:line 251
   at Microsoft.CodeAnalysis.MetadataReference.CreateFromFile(Stream peStream, String path, MetadataReferenceProperties properties, DocumentationProvider documentation) in /_/src/Compilers/Core/Portable/MetadataReference/MetadataReference.cs:line 258
   at Microsoft.CodeAnalysis.Scripting.Hosting.RuntimeMetadataReferenceResolver.<>c.<.ctor>b__11_0(String path, MetadataReferenceProperties properties) in /_/src/Scripting/Core/Hosting/Resolvers/RuntimeMetadataReferenceResolver.cs:line 92
   at Microsoft.CodeAnalysis.Scripting.Hosting.RuntimeMetadataReferenceResolver.CreateResolvedMissingReference(String fullPath) in /_/src/Scripting/Core/Hosting/Resolvers/RuntimeMetadataReferenceResolver.cs:line 141
   at Microsoft.CodeAnalysis.Scripting.Hosting.RuntimeMetadataReferenceResolver.ResolveMissingAssembly(MetadataReference definition, AssemblyIdentity referenceIdentity) in /_/src/Scripting/Core/Hosting/Resolvers/RuntimeMetadataReferenceResolver.cs:line 128
   at Microsoft.CodeAnalysis.Scripting.ScriptMetadataResolver.ResolveMissingAssembly(MetadataReference definition, AssemblyIdentity referenceIdentity) in /_/src/Scripting/Core/ScriptMetadataResolver.cs:line 68
   at Microsoft.CodeAnalysis.CommonReferenceManager`2.TryResolveMissingReference(MetadataReference requestingReference, AssemblyIdentity referenceIdentity, ImmutableDictionary`2& implicitReferenceResolutions, MetadataReferenceResolver resolver, DiagnosticBag resolutionDiagnostics, AssemblyIdentity& resolvedAssemblyIdentity, AssemblyMetadata& resolvedAssemblyMetadata, PortableExecutableReference& resolvedReference) in /_/src/Compilers/Core/Portable/ReferenceManager/CommonReferenceManager.Binding.cs:line 543
   at Microsoft.CodeAnalysis.CommonReferenceManager`2.ResolveAndBindMissingAssemblies(ImmutableArray`1 explicitAssemblies, MultiDictionary`2 explicitAssembliesMap, ImmutableArray`1 explicitModules, ImmutableArray`1 explicitReferences, ImmutableArray`1 explicitReferenceMap, MetadataReferenceResolver resolver, MetadataImportOptions importOptions, Boolean supersedeLowerVersions, ArrayBuilder`1 referenceBindings, Dictionary`2 assemblyReferencesBySimpleName, ImmutableArray`1& allAssemblies, ImmutableArray`1& metadataReferences, ImmutableArray`1& resolvedReferences, ImmutableDictionary`2& implicitReferenceResolutions, DiagnosticBag resolutionDiagnostics) in /_/src/Compilers/Core/Portable/ReferenceManager/CommonReferenceManager.Binding.cs:line 266
   at Microsoft.CodeAnalysis.CommonReferenceManager`2.Bind(ImmutableArray`1 explicitAssemblies, ImmutableArray`1 explicitModules, ImmutableArray`1 explicitReferences, ImmutableArray`1 explicitReferenceMap, MetadataReferenceResolver resolverOpt, MetadataImportOptions importOptions, Boolean supersedeLowerVersions, Dictionary`2 assemblyReferencesBySimpleName, ImmutableArray`1& allAssemblies, ImmutableArray`1& implicitlyResolvedReferences, ImmutableArray`1& implicitlyResolvedReferenceMap, ImmutableDictionary`2& implicitReferenceResolutions, DiagnosticBag resolutionDiagnostics, Boolean& hasCircularReference, Int32& corLibraryIndex) in /_/src/Compilers/Core/Portable/ReferenceManager/CommonReferenceManager.Binding.cs:line 134
   at Microsoft.CodeAnalysis.CSharp.CSharpCompilation.ReferenceManager.CreateAndSetSourceAssemblyFullBind(CSharpCompilation compilation) in /_/src/Com
Raw output
   at Microsoft.CodeAnalysis.Scripting.Test.ScriptingTestHelpers.AssertCompilationError(Action action, DiagnosticDescription[] expectedDiagnostics) in /_/src/Scripting/CoreTestUtilities/ScriptingTestHelpers.cs:line 95
   at Microsoft.CodeAnalysis.CSharp.Scripting.UnitTests.InteractiveSessionTests.StaticMethodCannotAccessGlobalInstance() in /_/src/Scripting/CSharpTest/InteractiveSessionTests.cs:line 1864

Check failure on line 1 in Microsoft.CodeAnalysis.CSharp.Features.UnitTests_Microsoft.CodeAnalysis.CSharp.IOperation.UnitTests_Microsoft.CodeAnalysis.CSharp.ExpressionEvaluator...._37.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / roslyn-CI

Microsoft.CodeAnalysis.CSharp.Features.UnitTests_Microsoft.CodeAnalysis.CSharp.IOperation.UnitTests_Microsoft.CodeAnalysis.CSharp.ExpressionEvaluator...._37.WorkItemExecution

The Helix Work Item failed. Often this is due to a test crash. Please see the 'Artifacts' tab above for additional logs.

Check failure on line 1 in Microsoft.CodeAnalysis.CSharp.Symbol.UnitTests_Microsoft.CodeAnalysis.CSharp.Syntax.UnitTests_Microsoft.CodeAnalysis.CSharp.Workspaces.UnitTests_Micro..._47.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / roslyn-CI

Microsoft.CodeAnalysis.CSharp.Symbol.UnitTests_Microsoft.CodeAnalysis.CSharp.Syntax.UnitTests_Microsoft.CodeAnalysis.CSharp.Workspaces.UnitTests_Micro..._47.WorkItemExecution

The Helix Work Item failed. Often this is due to a test crash. Please see the 'Artifacts' tab above for additional logs.