Skip to content

Add IsExternalInit back to Razor EA #77186

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.

Sign up for GitHub

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

Merged
tmat merged 1 commit into from
Feb 12, 2025

Add IsExternalInit back to Razor EA

fdb3c1d
Select commit
Loading
Failed to load commit list.
Merged

Add IsExternalInit back to Razor EA #77186

Add IsExternalInit back to Razor EA
fdb3c1d
Select commit
Loading
Failed to load commit list.
Build Analysis / Build Analysis succeeded Feb 12, 2025 in 0s

.NET Result Analysis

Details

All checks completed

✅ [roslyn-CI]

✅ [roslyn-integration-CI]

Build Rerun

✔️ Build passed after 1 retries.

(Attempt #1) [link to build]

roslyn-CI / Windows_Release_Desktop / Test_Windows_Desktop_Spanish_Release_64 / Run Unit Tests

[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]
    ❌(NETCORE_ENGINEERING_TELEMETRY=Test) Tests failed
    ❌PowerShell exited with code '1'.

Non-Deterministic Test Failures Detected

❌ Microsoft.CodeAnalysis.Editor.CSharp.UnitTests.Debugging.NameResolverTests.NegativeTests [Console] [Details] [Artifacts] [0.05% failure rate]
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]

Failing Configuration
Exception Message
System.OutOfMemoryException : Se produjo una excepción de tipo 'System.OutOfMemoryException'.
CallStack
   en Microsoft.CodeAnalysis.Editor.CSharp.UnitTests.Debugging.NameResolverTests.<NegativeTests>d__11.MoveNext()
   en System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[TStateMachine](TStateMachine& stateMachine)
   en Microsoft.CodeAnalysis.Editor.CSharp.UnitTests.Debugging.NameResolverTests.NegativeTests()
❌ Microsoft.CodeAnalysis.Editor.CSharp.UnitTests.Debugging.NameResolverTests.TestAllConstructors [Console] [Details] [Artifacts] [0.05% failure rate]
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]

Failing Configuration
Exception Message
System.OutOfMemoryException : Se produjo una excepción de tipo 'System.OutOfMemoryException'.
CallStack
   en Microsoft.CodeAnalysis.Editor.CSharp.UnitTests.Debugging.NameResolverTests.<TestAllConstructors>d__14.MoveNext()
   en System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[TStateMachine](TStateMachine& stateMachine)
   en Microsoft.CodeAnalysis.Editor.CSharp.UnitTests.Debugging.NameResolverTests.TestAllConstructors()
❌ Microsoft.CodeAnalysis.Editor.CSharp.UnitTests.Debugging.NameResolverTests.TestGenericNameInClassNamespace [Console] [Details] [Artifacts] [0.05% failure rate]
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]

Failing Configuration
Exception Message
System.OutOfMemoryException : Se produjo una excepción de tipo 'System.OutOfMemoryException'.
CallStack
   en Microsoft.CodeAnalysis.Editor.CSharp.UnitTests.Debugging.NameResolverTests.<TestGenericNameInClassNamespace>d__5.MoveNext()
   en System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[TStateMachine](TStateMachine& stateMachine)
   en Microsoft.CodeAnalysis.Editor.CSharp.UnitTests.Debugging.NameResolverTests.TestGenericNameInClassNamespace()

Was this helpful? Yes No

View more details on Build Analysis