Skip to content

[release/10.0]: Fix EC public key export for provider keys - #133956

Open
vcsjones wants to merge 1 commit into
dotnet:release/10.0from
vcsjones:ossl-provider-export-fix-release-10.0
Open

vcsjones wants to merge 1 commit into
dotnet:release/10.0from
vcsjones:ossl-provider-export-fix-release-10.0

Implement fix for ECC curve exports with the PKCS#11 Provider

b66e0ed
Select commit
Loading
Failed to load commit list.
Build Analysis / Helix Queue Insights (preview) succeeded Sep 15, 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
runtime-dev-innerloop 50 minutes, 28 seconds 59 minutes, 39 seconds 1 hour, 8 minutes, 50 seconds
dotnet-linker-tests 58 minutes, 1 second 1 hour, 45 minutes, 11 seconds 2 hours, 32 minutes, 22 seconds
runtime ❌ ❌ ❌

Pipelines denoted with ❌ means that this pipeline is highly variable, and we cannot predict its duration. This typically means this pipeline changes the legs it runs based on the PR's changed contents.

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
azurelinux.3.amd64.open.svc 29 minutes, 28 seconds 0.11% 📈
windows.amd64.server2022.open.svc 29 minutes, 2 seconds -0.33% 📉
windows.10.amd64.open.svc 10 minutes, 21 seconds -0.72% 📉
windows.server2025.amd64.open.svc 9 minutes, 26 seconds -0.82% 📉
windows.11.amd64.android.open 3 minutes, 9 seconds -0.7% 📉

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

Was this helpful? Yes No