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

Make ReflectionAccessAnalyzer logic more similar to ILLink/ILC #105956

Merged
merged 2 commits into from
Aug 6, 2024

Avoid DiagnosticContext in ReflectionAccessAnalyzer

d42e9b7
Select commit
Loading
Failed to load commit list.
Merged

Make ReflectionAccessAnalyzer logic more similar to ILLink/ILC #105956

Avoid DiagnosticContext in ReflectionAccessAnalyzer
d42e9b7
Select commit
Loading
Failed to load commit list.
Azure Pipelines / runtime failed Aug 5, 2024 in 3h 10m 2s

Build #20240805.58 had test failures

Details

Tests

  • Failed: 14 (0.00%)
  • Passed: 560,739 (96.73%)
  • Other: 18,927 (3.27%)
  • Total: 579,680

Annotations

Check failure on line 19 in .dotnet/sdk/9.0.100-preview.6.24328.19/NuGet.RestoreEx.targets

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

.dotnet/sdk/9.0.100-preview.6.24328.19/NuGet.RestoreEx.targets#L19

.dotnet/sdk/9.0.100-preview.6.24328.19/NuGet.RestoreEx.targets(19,5): error : (NETCORE_ENGINEERING_TELEMETRY=Restore) Unhandled exception. Microsoft.Build.Framework.InternalErrorException: MSB0001: Internal MSBuild Error: must be valid

Check failure on line 19 in .dotnet/sdk/9.0.100-preview.6.24328.19/NuGet.RestoreEx.targets

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

.dotnet/sdk/9.0.100-preview.6.24328.19/NuGet.RestoreEx.targets#L19

.dotnet/sdk/9.0.100-preview.6.24328.19/NuGet.RestoreEx.targets(19,5): error : (NETCORE_ENGINEERING_TELEMETRY=Restore)    at Microsoft.Build.Shared.ErrorUtilities.ThrowInternalError(String message, Exception innerException, Object[] args)

Check failure on line 19 in .dotnet/sdk/9.0.100-preview.6.24328.19/NuGet.RestoreEx.targets

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

.dotnet/sdk/9.0.100-preview.6.24328.19/NuGet.RestoreEx.targets#L19

.dotnet/sdk/9.0.100-preview.6.24328.19/NuGet.RestoreEx.targets(19,5): error : (NETCORE_ENGINEERING_TELEMETRY=Restore)    at Microsoft.Build.BackEnd.Logging.LoggingContext.LogBuildEvent(BuildEventArgs buildEvent)

Check failure on line 19 in .dotnet/sdk/9.0.100-preview.6.24328.19/NuGet.RestoreEx.targets

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

.dotnet/sdk/9.0.100-preview.6.24328.19/NuGet.RestoreEx.targets#L19

.dotnet/sdk/9.0.100-preview.6.24328.19/NuGet.RestoreEx.targets(19,5): error : (NETCORE_ENGINEERING_TELEMETRY=Restore)    at Microsoft.Build.BackEnd.Components.RequestBuilder.AssemblyLoadsTracker.CurrentDomainOnAssemblyLoad(Object sender, AssemblyLoadEventArgs args)

Check failure on line 1 in Wasm.Build.Tests.WasmBuildAppTest.PropertiesFromCsproj

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

Wasm.Build.Tests.WasmBuildAppTest.PropertiesFromCsproj

Test failed

Check failure on line 1 in Wasm.Build.Tests.IcuShardingTests.AutomaticShardSelectionDependingOnEnvLocale

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

Wasm.Build.Tests.IcuShardingTests.AutomaticShardSelectionDependingOnEnvLocale

Test failed

Check failure on line 1 in Workloads-ST-Wasm.Build.Tests.IcuShardingTests.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

Workloads-ST-Wasm.Build.Tests.IcuShardingTests.WorkItemExecution

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

Check failure on line 1 in Workloads-ST-Wasm.Build.Tests.WasmBuildAppTest.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

Workloads-ST-Wasm.Build.Tests.WasmBuildAppTest.WorkItemExecution

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