Repository navigation
[release/10.0] Disable SDK certificate generation in macOS Helix - #70542
Merged
wtgodbe merged 1 commit intoNov 12, 2026
Conversation
Avoid automatic HTTPS certificate initialization before macOS Helix SDK setup and discovery commands. Preserve other platforms and explicit certificate generation. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
🔵 Needs a closer look
Pending macOS x64 Helix validation leaves it unconfirmed whether disabling automatic certificate provisioning resolves the native startup stall while preserving HTTPS/certificate tests.
No open issues 🎉
What changed in this PR
Disables automatic SDK HTTPS certificate generation in macOS Helix work items to avoid first-run certificate/keychain initialization stalls before tests execute.
Changes:
- Exports
DOTNET_GENERATE_ASPNET_CERTIFICATE=falsewhen the Helix queue name containsOSX, before SDK commands run. - Leaves other platforms, queue selections, and explicit certificate-generation APIs unchanged.
Full validation on the affected macOS x64 Helix pool, including HTTPS/certificate tests, remains pending.
| File | Description |
|---|---|
eng/helix/content/runtests.sh |
Adds the macOS-only SDK certificate-generation opt-out. |
Review effort: Balanced
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Skip automatic SDK HTTPS certificate generation in macOS Helix.
Description
Export
DOTNET_GENERATE_ASPNET_CERTIFICATE=falsefor macOS Helix work items before invoking the SDK. Leave other platforms, queue selections, and explicit certificate-generation APIs unchanged.The investigation of #70521 found SDK commands stalling during first-run HTTPS certificate initialization. The runner then cancels each setup/discovery command after two minutes with exit code 130, before any tests execute. The existing
DOTNET_SKIP_FIRST_TIME_EXPERIENCE=1does not suppress certificate initialization on these SDKs. The same signature also occurs on the release/10.0 baseline.Representative failed Helix work item.
This avoids unnecessary automatic certificate/keychain operations; it does not identify or fix the underlying native wait.
Validation
bash -n eng/helix/content/runtests.shandgit diff --checkpassed.Draft pending full macOS Helix validation on the affected x64 pool, including HTTPS/certificate tests. Local smoke checks are not a substitute for that CI run.