[Diagnostics] Add InProc CrashReport Logging #128105
Open
Build Analysis / Build Analysis
failed
May 15, 2026 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.
Known Repository Errors
Known Infrastructure Errors
-
❌20260514.118 / Build / linux-x64 Debug NativeAOT / Send tests to Helix (Unix) and 35 more hits - The Operation will be canceled. The next steps may not contain expected logs.
Build Failures
runtime / Build / linux-x64 Debug NativeAOT
[ 🚧 Create issue against infrastructure team] [ 📄 Create issue in this repo]-
❌The job running on agent NetCore-Public 286 ran longer than the maximum time of 180 minutes. For more information, see https://go.microsoft.com/fwlink/?linkid=2077134
runtime / Build / windows-x64 Debug NativeAOT
[ 🚧 Create issue against infrastructure team] [ 📄 Create issue in this repo]-
❌The job running on agent NetCore-Public 30 ran longer than the maximum time of 180 minutes. For more information, see https://go.microsoft.com/fwlink/?linkid=2077134
runtime / Build / windows-x64 Checked NativeAOT
[ 🚧 Create issue against infrastructure team] [ 📄 Create issue in this repo]-
❌The job running on agent NetCore-Public 749 ran longer than the maximum time of 180 minutes. For more information, see https://go.microsoft.com/fwlink/?linkid=2077134
25 other jobs are failing and were not displayed due to space limitations.
Builds with failures: [runtime]
Was this helpful?
Loading