microsoft / microsoft/aspire

[CI Failure] GitHub artifact upload fails with ETIMEDOUT network timeout

Open
#19,876 1 comment 0 reactions 0 assignees View on GitHub
ci-failure-cause
Dominant language
C#
Stars
6.3k
Forks
991
Avg merge
2d 15h
Merged PRs (30d)
196

Description

## Build Information

Build: https://github.com/microsoft/aspire/actions/runs/33671638017
Build error leg: Tests / No-package tests (regular, Aspire.Hosting.Sdk.Tests, Hosting.Sdk, Hosting.Sdk, tests/Aspire.Hosti... / Hosting.Sdk (windows-latest)
Pull request: #19403

## Error Message

```
Failed to CreateArtifact: Unable to make request: ETIMEDOUT
If you are using self-hosted runners, please make sure your runner has access to all GitHub endpoints
```

## Description

GitHub artifact upload fails with ETIMEDOUT network timeout

**Type**: infra-failure

## Occurrences

| Date | Build | Job | PR |
|------|-------|-----|----|
| 2026-09-02 | [33671638017](https://github.com/microsoft/aspire/actions/runs/33671638017) | Tests / No-package tests (regular, Aspire.Hosting.Sdk.Tests, Hosting.Sdk, Hosting.Sdk, tests/Aspire.Hosti... / Hosting.Sdk (windows-latest) | #19403 |
| 2026-09-10 | [34432786645](https://github.com/microsoft/aspire/actions/runs/34432786645) | Tests / Package tests - macOS (class, Aspire.Templates.Tests, Templates-XUnit_V3MTP_NewUpAndBuildSupportP... / Templates-XUnit_V3MTP_NewUpAndBuildSupportProjectTemplatesTests (macos-latest) | #19999 |
| 2026-09-10 | [34519005883](https://github.com/microsoft/aspire/actions/runs/34519005883) | Tests / No-package tests (regular, Aspire.Hosting.RemoteHost.Tests, Hosting.RemoteHost, Hosting.RemoteHos... / Hosting.RemoteHost (windows-latest) | #20040 |

Contributor guide

Open the contributing guide

Research direction

Start by reviewing build runs 33671638017, 34432786645, and 34519005883, focusing on the listed Windows and macOS test jobs and their artifact-upload steps. Compare the runner and network conditions around each ETIMEDOUT failure; done means the affected CI jobs can upload artifacts reliably or the failure is otherwise handled and verified in a rerun.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.