Restore E_NOTIMPL fallback in DacDbiInterfaceImpl::GetContext #128499

View the current status of Helix

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

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	51 minutes, 34 seconds	57 minutes, 6 seconds	1 hour, 2 minutes, 38 seconds
runtime	1 hour, 23 minutes, 38 seconds	2 hours, 23 minutes, 49 seconds	3 hours, 24 minutes
dotnet-linker-tests	48 minutes, 2 seconds	1 hour, 35 minutes, 4 seconds	2 hours, 22 minutes, 6 seconds

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.15.amd64.open	1 hour, 40 minutes, 56 seconds	0.08% 📈
windows.10.amd64.open.rt	1 hour, 1 minute	-0.31% 📉
windows.11.amd64.android-armel.open	32 minutes, 50 seconds	-0.34% 📉
windows.10.amd64.client.open.rt	29 minutes, 40 seconds	0.17% 📈
azurelinux.3.arm64.open	29 minutes, 17 seconds	-0.13% 📉

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

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

dotnet/runtime uses the following on-prem queues:

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

_{Was this helpful?}