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

NativeAOT the XUnitLogChecker #103795

Merged
merged 17 commits into from
Aug 30, 2024

Update eng/testing/RunnerTemplate.cmd

f10a4e3
Select commit
Loading
Failed to load commit list.
Merged

NativeAOT the XUnitLogChecker #103795

Update eng/testing/RunnerTemplate.cmd
f10a4e3
Select commit
Loading
Failed to load commit list.
Build Analysis / Helix Queue Insights (preview) succeeded Aug 30, 2024 in 0s

View the current status of Helix

Details

Pipeline Status

The list of queues is cached weekly. If your PR changes what queues your pipelines use, this information will not show the updated queues.

Estimated Pipeline Durations

This model assumes that the current state of the entire CI infrastructure is normal, and that your CI pipelines will succeed.

Pipeline Lower Bound Estimated Time Upper Bound
dotnet-linker-tests 44 minutes, 13 seconds 59 minutes, 47 seconds 1 hour, 15 minutes, 22 seconds
runtime-dev-innerloop 37 minutes, 47 seconds 53 minutes, 24 seconds 1 hour, 9 minutes, 2 seconds
runtime 57 minutes, 33 seconds 1 hour, 47 minutes, 22 seconds 2 hours, 37 minutes, 11 seconds

Highest Work Item Wait Time Queues

Here's a list of the top 5 queues with the highest work item wait time:

Queue Work Item Wait Time Difference in Moving Avg
osx.13.amd64.appletv.open 2 hours, 15 minutes, 51 seconds 0.27% 📈
windows.81.amd64.open.rt 48 minutes, 14 seconds 0.09% 📈
windows.11.arm64.open 43 minutes, 32 seconds -0.03% 📉
ubuntu.2004.armarch.open 37 minutes, 11 seconds -0.1% 📉
windows.10.amd64.serverrs5.open.rt 34 minutes, 47 seconds -0.29% 📉

Grafana Dashboard

For more in-depth information on the status of Helix, visit our Grafana Dashboard.

Your Queues

☁️ Helix Queues

dotnet/runtime is currently configured to submit to the following Helix queues:

🏢 On Premises Helix Queues

dotnet/runtime uses the following on-prem queues:

Build Pools

Microsoft Hosted

This pipeline will build on the following Microsoft Hosted build pools:

Click here for information about these agents.

  • ubuntu-22.04
  • ubuntu-latest
  • macOS-latest
  • macOS-12

Was this helpful? Yes No