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.

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

Move HasHome out of Binder #75851

Merged
merged 3 commits into from
Nov 12, 2024

Add a comment

c699cdb
Select commit
Loading
Failed to load commit list.
Merged

Move HasHome out of Binder #75851

Add a comment
c699cdb
Select commit
Loading
Failed to load commit list.
Build Analysis / Build Analysis succeeded Nov 11, 2024 in 0s

.NET Result Analysis

Details

All checks completed

✅ [roslyn-CI]

Build Rerun

✔️ Build passed after 1 retries.

(Attempt #1) [link to build]

roslyn-CI / Windows_Release_Desktop / Test_Windows_Desktop_Release_32 / 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.CSharp.Symbol.UnitTests_Microsoft.CodeAnalysis.CSharp.Syntax.UnitTests_Microsoft.CodeAnalysis.CSharp.Workspaces.UnitTests_Micro..._40.WorkItemExecution [Console] [Details] [Artifacts] [1.85% failure rate]
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
This is a helix work item crash with status: BadExit. To investigate look the [Console log] / navigate to [Helix Artifacts]

Failing Configuration
❌ Microsoft.CodeAnalysis.Editor.UnitTests.RenameTracking.RenameTrackingTaggerProviderTests.RenameTrackingHandlesSquareBracketsAsVisualBasicEscape [Console] [Details] [Artifacts] [0.07% failure rate]
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]

Failing Configuration
Exception Message
Assert.Equal() Failure: Values differ
Expected: 1
Actual:   0
CallStack
   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.<RenameTrackingHandlesSquareBracketsAsVisualBasicEscape>d__13.MoveNext() in /_/src/EditorFeatures/Test/RenameTracking/RenameTrackingTaggerProviderTests.cs:line 215
--- 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 System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(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)

Was this helpful? Yes No

View more details on Build Analysis