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

[release/9.0-rc1] Update dependencies from dotnet/roslyn-analyzers #106499

Update dependencies from https://github.com/dotnet/roslyn-analyzers b…

1dd6243
Select commit
Loading
Failed to load commit list.
Merged

[release/9.0-rc1] Update dependencies from dotnet/roslyn-analyzers #106499

Update dependencies from https://github.com/dotnet/roslyn-analyzers b…
1dd6243
Select commit
Loading
Failed to load commit list.
Build Analysis / Build Analysis succeeded Aug 15, 2024 in 0s

.NET Result Analysis

Details

‼️ Build Analysis Check Result has been manually overridden

  • The build analysis check result has been updated by the user for the following reason: failures are known (https://github.com//issues/106160 and https://github.com//issues/106160), but the release branches are not getting Build Analysis triggered as expected cc @JulieLeeMSFT
  • The check result has changed from Failure to Success

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.

⚠️ The following pipeline(s) will not be analyzed as has been explicited excluded from analysis

Build Failures

runtime / Build / windows-arm64 release CrossAOT_Mono crossaot / Build product

[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]
    ❌src\mono\mono.proj(1027,5): error MSB3073: The command "call "D:\a\_work\1\s\eng\native\init-vs-env.cmd" arm64 && cd /D "D:\a\_work\1\s\artifacts\obj\mono\android.x64.Release\cross\" && cmake --build . --target install --config Release" exited with code 1.

Known test errors

Test Failures (2 tests failed)

🔹 [All failing tests from runtime]

Was this helpful? Yes No