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

Haiku: Update arcade support #13755

Merged

Haiku: Update arcade support

6d1d15d
Select commit
Failed to load commit list.
Merged

Haiku: Update arcade support #13755

Haiku: Update arcade support
6d1d15d
Select commit
Failed to load commit list.
Build Analysis / Helix Queue Insights (preview) succeeded Aug 20, 2023 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
arcade-ci 34 minutes, 32 seconds 49 minutes 1 hour, 3 minutes, 29 seconds

Highest Work Item Wait Time Queues

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

Queue Work Item Wait Time Difference in Moving Avg
windows.10.amd64.open.arcade 21 minutes, 54 seconds 0.01% 📈
ubuntu.2204.amd64.open 7 minutes, 52 seconds -0.81% 📉

Grafana Dashboard

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

Your Queues

☁️ Helix Queues

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

🏢 On Premises Helix Queues

dotnet/arcade 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
  • windows-2022
  • windows-latest

Was this helpful? Yes No