dotnet / dotnet/dotnet

[Operational Issue]: OSX_arm64 scenario tests repeatedly time out after 30 minutes

Open
#8,080 2 comments 0 reactions 0 assignees View on GitHub
area-unified-build-OperationalIssue Priority:1
Dominant language
C#
Stars
1.3k
Forks
337
Avg merge
6h 41m
Merged PRs (30d)
949

Description

### Error

The `OSX_arm64` official-build leg times out during scenario tests after 30 minutes:

```text
##[error]The task has timed out.
```

The timeout occurs while running `src/scenario-tests/eng/common/build.sh --test`. This occurred in 4 `main` shipping builds during the last 8 days.

### Links

- Latest: https://dev.azure.com/dnceng/internal/_build/results?buildId=3035767
- https://dev.azure.com/dnceng/internal/_build/results?buildId=3032897
- https://dev.azure.com/dnceng/internal/_build/results?buildId=3031984
- https://dev.azure.com/dnceng/internal/_build/results?buildId=3030052

### Root Cause

Unknown. The test task reaches its 30-minute timeout without reporting a test failure.

### Blocking

- [ ] This issue is blocking

### Affected Releases

- [ ] .NET 10
- [ ] .NET 10 (SDK band build)
- [x] .NET 11

Contributor guide

Open the contributing guide

Research direction

Start with src/scenario-tests/eng/common/build.sh --test and compare the four linked OSX_arm64 shipping-build results, focusing on where execution reaches the 30-minute timeout without a reported test failure. Done means identifying the cause and ensuring the OSX_arm64 scenario-test leg completes without timing out.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, shell
Domain
build-system, ci-cd, testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.