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

Jump to bottom

Ensure NFW gets reported before result is reported to client and remove async listener in queue #75907

Merged
merged 3 commits into from
Nov 15, 2024

adjust comment

ea7c07a
Select commit
Loading
Failed to load commit list.
Merged

Ensure NFW gets reported before result is reported to client and remove async listener in queue #75907

adjust comment
ea7c07a
Select commit
Loading
Failed to load commit list.
Azure Pipelines / roslyn-CI succeeded Nov 14, 2024 in 37m 47s

Build #20241114.30 had test failures

1 errors / 18 warnings

Details

Tests

  • Failed: 2 (0.00%)
  • Passed: 948,627 (98.81%)
  • Other: 11,430 (1.19%)
  • Total: 960,059

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.CompilerServer.UnitTests.CompilerServerUnitTests.ReferenceCachingCS

See this annotation in the file changed.

@azure-pipelines azure-pipelines / roslyn-CI

Microsoft.CodeAnalysis.CompilerServer.UnitTests.CompilerServerUnitTests.ReferenceCachingCS 

System.IO.IOException : The process cannot access the file 'C:hwB039097A	RoslynTests7298fb8-e605-4c0e-91c4-d5403ef1223fReferenceCachingCShello1.exe' because it is being used by another process.
Raw output 
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.File.InternalDelete(String path, Boolean checkHost)
   at System.IO.File.Delete(String path)
   at Microsoft.CodeAnalysis.Test.Utilities.DisposableFile.Dispose() in /_/src/Compilers/Test/Core/TempFiles/DisposableFile.cs:line 29
   at Microsoft.CodeAnalysis.CompilerServer.UnitTests.CompilerServerUnitTests.<ReferenceCachingCS>d__43.MoveNext() in /_/src/Compilers/Server/VBCSCompilerTests/CompilerServerTests.cs:line 952
--- 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)

Check failure on line 1 in Microsoft.VisualStudio.LanguageServices.UnitTests_Roslyn.Compilers.VisualBasic.IOperation.UnitTests_Roslyn.VisualStudio.Next.UnitTests_SemanticSearch...._67.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / roslyn-CI

Microsoft.VisualStudio.LanguageServices.UnitTests_Roslyn.Compilers.VisualBasic.IOperation.UnitTests_Roslyn.VisualStudio.Next.UnitTests_SemanticSearch...._67.WorkItemExecution 

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