Skip to content

[release/9.0] (deps): Bump src/submodules/googletest from d72f9c8 to add971c#66786

Closed
dependabot[bot] wants to merge 1 commit into
release/9.0from
dependabot/submodules/release/9.0/src/submodules/googletest-add971c
Closed

[release/9.0] (deps): Bump src/submodules/googletest from d72f9c8 to add971c#66786
dependabot[bot] wants to merge 1 commit into
release/9.0from
dependabot/submodules/release/9.0/src/submodules/googletest-add971c

[release/9.0] (deps): Bump src/submodules/googletest

765db01
Select commit
Loading
Failed to load commit list.
Build Analysis / Helix Queue Insights (preview) succeeded May 21, 2026 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
aspnetcore-ci 30 minutes, 41 seconds 1 hour, 12 minutes, 54 seconds 1 hour, 55 minutes, 6 seconds

Highest Work Item Wait Time Queues

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

Queue Work Item Wait Time Difference in Moving Avg
windows.11.amd64.client.open.svc 28 minutes, 51 seconds -0.13% 📉
osx.15.amd64.open 23 minutes, 20 seconds -0.96% 📉
ubuntu.2204.amd64.open.svc 17 minutes, 10 seconds -0.9% 📉
windows.amd64.vs2022.open.svc 16 minutes, 45 seconds -0.1% 📉

Grafana Dashboard

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

Your Queues

☁️ Helix Queues

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

🏢 On Premises Helix Queues

dotnet/aspnetcore uses the following on-prem queues:

Build Pools

Was this helpful? Yes No