JIT: Change VN's representation for phi definitions #105198
Build #20240721.22 had test failures
Details
- Failed: 1 (0.00%)
- Passed: 986,154 (98.41%)
- Other: 15,954 (1.59%)
- Total: 1,002,109
Annotations
Check failure on line 115 in Build log
azure-pipelines / runtime
Build log #L115
Failed to generate "CoreCLR component" build project!
Check failure on line 108 in src/coreclr/runtime.proj
azure-pipelines / runtime
src/coreclr/runtime.proj#L108
src/coreclr/runtime.proj(108,5): error MSB3073: (NETCORE_ENGINEERING_TELEMETRY=Build) The command ""/__w/1/s/src/coreclr/build-runtime.sh" -armel -checked -ci -cross -portablebuild=false -os linux -outputrid tizen.9.0.0-armel -cmakeargs "-DCLR_DOTNET_HOST_PATH=/__w/1/s/.dotnet/dotnet" -cmakeargs "-DCDAC_BUILD_TOOL_BINARY_PATH=/__w/1/s/artifacts/bin/coreclr/linux.armel.Checked/cdac-build-tool/cdac-build-tool.dll"" exited with code 1.
Check failure on line 0 in CSC
azure-pipelines / runtime
CSC#L0
CSC(0,0): error AD0001: (NETCORE_ENGINEERING_TELEMETRY=Build) Analyzer 'Microsoft.NetCore.Analyzers.Runtime.ModuleInitializerAttributeShouldNotBeUsedInLibraries' threw an exception of type 'System.AccessViolationException' with message 'Attempted to read or write protected memory. This is often an indication that other memory is corrupt.'.
azure-pipelines / runtime
.packages/microsoft.dotnet.helix.sdk/9.0.0-beta.24360.4/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets#L91
.packages/microsoft.dotnet.helix.sdk/9.0.0-beta.24360.4/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item System.Net.NameResolution.Functional.Tests in job 2b0e0759-bdc2-4c54-857c-dc7b32548620 has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/2b0e0759-bdc2-4c54-857c-dc7b32548620/workitems/System.Net.NameResolution.Functional.Tests/console
Check failure on line 1 in System.Net.NameResolution.Functional.Tests.WorkItemExecution
azure-pipelines / runtime
System.Net.NameResolution.Functional.Tests.WorkItemExecution
The Helix Work Item failed. Often this is due to a test crash. Please see the 'Artifacts' tab above for additional logs.