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

Delete dead Interop.Gdi32.* code #105209

Merged
merged 1 commit into from
Jul 22, 2024

Delete seemingly dead Interop.Gdi32.* code

7575e2e
Select commit
Loading
Failed to load commit list.
Merged

Delete dead Interop.Gdi32.* code #105209

Delete seemingly dead Interop.Gdi32.* code
7575e2e
Select commit
Loading
Failed to load commit list.
Build Analysis / Helix Queue Insights (preview) succeeded Jul 22, 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
runtime-dev-innerloop 33 minutes, 27 seconds 54 minutes, 58 seconds 1 hour, 16 minutes, 29 seconds
dotnet-linker-tests 42 minutes, 33 seconds 1 hour, 25 seconds 1 hour, 18 minutes, 16 seconds
runtime 59 minutes, 57 seconds 1 hour, 49 minutes, 17 seconds 2 hours, 38 minutes, 36 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
windows.10.amd64.serverrs5.open.rt 40 minutes, 20 seconds -0.31% 📉
windows.81.amd64.open.rt 28 minutes, 49 seconds -0.18% 📉
windows.10.amd64.client.open.rt 28 minutes, 40 seconds 0.01% 📈
windows.amd64.server2022.open.rt 28 minutes, 11 seconds -0.44% 📉
windows.11.arm64.open 25 minutes, 34 seconds -0.44% 📉

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:

⚠️ We failed to query some work item wait times.

This typically means there hasn't been any recent work submitted to these queues. If this looks wrong, please contact @dnceng.

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