Add SetEntryAssembly()
API to System.Reflection
#102271
Merged
Build Analysis / Build Analysis
failed
May 17, 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.
⚠️ The following pipeline(s) will not be analyzed as has been explicited excluded from analysis
Build Failures
runtime / Build / linux_musl-x64 Debug CoreCLR_Libraries / Build product
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌src/libraries/System.Runtime/tests/System.Reflection.Tests/AssemblyTests.cs(15,24): error CS0234: The type or namespace name 'RemoteExecutor' does not exist in the namespace 'Microsoft.DotNet' (are you missing an assembly reference?)
runtime / Build / linux-x64 Debug CoreCLR_Libraries / Build product
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌src/libraries/System.Runtime/tests/System.Reflection.Tests/AssemblyTests.cs(15,24): error CS0234: The type or namespace name 'RemoteExecutor' does not exist in the namespace 'Microsoft.DotNet' (are you missing an assembly reference?)
runtime / Build / osx-x64 Debug CoreCLR_Libraries / Build product
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌src/libraries/System.Runtime/tests/System.Reflection.Tests/AssemblyTests.cs(15,24): error CS0234: The type or namespace name 'RemoteExecutor' does not exist in the namespace 'Microsoft.DotNet' (are you missing an assembly reference?)
21 other jobs are failing and were not displayed due to space limitations.
Builds with failures: [runtime]
Loading