Skip to content

Report diagnostic for field and value as primary expressions only

Build Analysis / Build Analysis failed Jun 26, 2024 in 0s

.NET Result Analysis

Details

Tip

To unconditionally bypass the build analysis check (turn it green), you can use the escape mechanism feature. The completion time may vary, potentially taking several minutes, depending on the build analysis workload at the moment.

Build Failures

roslyn-CI / Correctness / Correctness_Analyzers / Build with analyzers

[ 🚧 Report infrastructure issue] [ πŸ“„ Report repository issue]
    ❌src/Compilers/CSharp/Portable/Binder/Binder_Statements.cs(1193,177): error IDE0060: Remove unused parameter 'diagnostics' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/style-rules/ide0060)

roslyn-CI / Correctness / Correctness_Bootstrap_Build_Default / Build - Validate Correctness

[ 🚧 Report infrastructure issue] [ πŸ“„ Report repository issue]
    ❌src\Compilers\CSharp\Portable\Binder\Binder_Statements.cs(1193,177): error IDE0060: Remove unused parameter 'diagnostics' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/style-rules/ide0060)
    ❌src\Tools\SemanticSearch\ReferenceAssemblies\SemanticSearch.ReferenceAssemblies.csproj(56,5): error : Assembly 'Microsoft.CodeAnalysis.CSharp' not found among project references
    ❌src\Tools\SemanticSearch\ReferenceAssemblies\SemanticSearch.ReferenceAssemblies.csproj(56,5): error : Assembly 'Microsoft.CodeAnalysis' not found among project references

Test Failures (2 tests failed)

πŸ”Ή [All failing tests from roslyn-CI]

Was this helpful? Yes No