dotnet / dotnet/dnceng

[macOS 26] dotnet dev-certs fails to save HTTPS developer certificate in Helix

Open
#6,723 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
31
Forks
38
Avg merge
1d 20h
Merged PRs (30d)
24

Description

## Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1586491
Leg Name: `browser-wasm osx Release LibraryTests_SmokeMac - osx.26.arm64.open`

Also observed in https://dev.azure.com/dnceng-public/public/_build/results?buildId=1584957, where the affected work item passed after Helix resubmission.

## Error Details

The WASM test work item fails during environment setup, before tests execute:

```text
+ dotnet dev-certs https
There was an error saving the HTTPS developer certificate to the current user personal certificate store.
+ export _commandExitCode=2
```

Confirmed occurrences:

- Build 1586491: `WasmTestOnChrome-MONO-ST-System.Runtime.Intrinsics.Tests` on `dci-mac-build-480`, macOS 26.4.1
- Build 1584957: `WasmTestOnChrome-MONO-ST-System.Runtime.InteropServices.JavaScript.Tests` on `dci-mac-build-462`, macOS 26.4; the resubmitted work item passed

The subsequent missing `xharness-event-processor.py` message is secondary to the setup command exiting with code 2.

## Error Message

```json
{
"ErrorMessage": "There was an error saving the HTTPS developer certificate to the current user personal certificate store.",
"BuildRetry": true,
"ExcludeConsoleLog": false
}
```

> [!NOTE]
> This issue was drafted and filed with GitHub Copilot.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the Helix environment setup command `dotnet dev-certs https` and the failed Build 1586491 work item on macOS 26.4.1. Compare it with the resubmitted Build 1584957 work item, where the command succeeded, and determine what setup change is needed so the certificate is saved and the WASM smoke tests can proceed.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos
Domain
ci-cd, infrastructure, testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.