CI: MAUI R2R Helix device-lab failures across Android queues
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 35/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- android
- 领域
- ci-cd, mobile-dev, testing
调研方向
首先重新运行公开的 dotnet-android PR 管道，并检查链接的 Helix work-item 控制台中的 MAUI R2R 任务。将主机和设备分配情况与授权、包管理器以及缺少设备的日志特征进行比较。当受影响的设备已获得授权且可用、其包管理器状态正常，并且在两个 Android 队列中重复运行均通过时，即表示完成。
由索引模型根据 Issue 内容生成。
描述
Android framework version
.NET 11 / net11.0-android CI builds.
Affected platform version
Helix queues:
windows.11.amd64.android.open(Android ARM64 devices)windows.11.amd64.android-armel.open(Android ARM32 devices)
Sample window: the latest 100 completed public dotnet-android pipeline builds at the time of investigation, from 2026-08-31 through 2026-09-03.
Description
Recent non-fork PR builds are frequently failing in Run MAUI R2R APKs on Helix. These failures are not Helix submission/authentication failures and do not demonstrate MAUI or ReadyToRun regressions: each job was submitted and scheduled successfully, then failed on device setup before the APK launch and pidof smoke check.
Of 92 sampled builds containing the task, 72 passed, 19 failed, and 1 was skipped. Eight of the failures were the separately understood fork-token problem. The remaining 11 direct-PR builds contained 12 failed work items:
- 8 Android package-manager/UID exhaustion failures
- 3 ADB authorization timeouts
- 1 missing-device timeout
| Build / PR | Configuration | Helix queue | Helix machine | Android device | Cause |
|---|---|---|---|---|---|
| #1579911 / #12650 | android-arm/Default | windows.11.amd64.android-armel.open |
DNCENGWIN-141 |
27091JEGR21946 (unauthorized) |
ADB unauthorized timeout |
| #1579675 / #12644 | android-arm/Full R2R | windows.11.amd64.android-armel.open |
DNCENGWIN-141 |
27091JEGR21946 (unauthorized) |
ADB unauthorized timeout |
| #1578760 / #12597 | android-arm64/Full R2R | windows.11.amd64.android.open |
DNCENGWIN-135 |
26081FDF60041K (Pixel 6) |
Package manager / UID exhaustion |
| #1578755 / #12641 | android-arm64/Default | windows.11.amd64.android.open |
DNCENGWIN-036 |
01XAYV0UJJ (Pixel 3a) |
Package manager / UID exhaustion |
| #1578133 / #12631 | android-arm64/Default | windows.11.amd64.android.open |
DNCENGWIN-006 |
9CJAY1PSW4 (Pixel 3a) |
Package manager / UID exhaustion |
| #1578128 / #12638 | android-arm64/Full R2R | windows.11.amd64.android.open |
DNCENGWIN-135 |
26081FDF60041K (Pixel 6) |
Package manager / UID exhaustion |
| #1577702 / #12629 | android-arm64/Default | windows.11.amd64.android.open |
DNCENGWIN-137 |
26091FDF6001Y5 (Pixel 6) |
Package manager / UID exhaustion |
| #1577702 / #12629 | android-arm/Full R2R | windows.11.amd64.android-armel.open |
DNCENGWIN-141 |
27091JEGR21946 (unauthorized) |
ADB unauthorized timeout |
| #1576771 / #12585 | android-arm64/Default | windows.11.amd64.android.open |
DNCENGWIN-036 |
01XAYV0UJJ (Pixel 3a) |
Package manager / UID exhaustion |
| #1576613 / #12614 | android-arm64/Full R2R | windows.11.amd64.android.open |
DNCENGWIN-034 |
None detected | No Android device timeout |
| #1576382 / #12541 | android-arm64/Default | windows.11.amd64.android.open |
DNCENGWIN-020 |
9CBAY1NP1W (Pixel 3a) |
Package manager / UID exhaustion |
| #1575529 / #12604 | android-arm64/Full R2R | windows.11.amd64.android.open |
DNCENGWIN-010 |
94SAY0SM1M (Pixel 3a) |
Package manager / UID exhaustion |
The ARM32 authorization failures are concentrated on one host/device pair: DNCENGWIN-141 / 27091JEGR21946.
The ARM64 failures are broader. adb uninstall first reports:
Failure [DELETE_FAILED_INTERNAL_ERROR]
The subsequent installation then fails with:
INSTALL_FAILED_INSUFFICIENT_STORAGE: Scanning Failed.: Package ... could not be assigned a valid UID
This signature occurred on seven Helix machines and six Android devices (Pixel 3a and Pixel 6 models).
Same-commit reruns also show infrastructure flakiness:
- PR #12597: failed in build 1578760, MAUI task passed in 1579125
- PR #12629: failed in build 1577702, passed in 1578074
- PR #12641: failed in build 1578755, MAUI task passed in 1579094 and 1579507
Steps to Reproduce
Run the public dotnet-android PR pipeline repeatedly. In the affected MAUI Tests > MAUI Integration > Run MAUI R2R APKs on Helix task, inspect the linked failed Helix work-item console.
The failures are intermittent and tied to the assigned Helix host/device rather than a known source change.
Did you find any workaround?
Rerun the pipeline so that Helix schedules the work item on a healthy device.
For the device lab:
- quarantine or re-authorize Android device
27091JEGR21946onDNCENGWIN-141 - clean/reprovision the affected ARM64 devices' package-manager state
- ensure a device is attached and authorized before assigning work to
DNCENGWIN-034
Relevant log output
ARM32 authorization failure:
List of devices attached
27091JEGR21946 unauthorized transport_id:1
adb.exe wait-for-device
END OF WORK ITEM LOG: Command timed out, and was killed
ARM64 package-manager failure:
adb.exe uninstall com.xamarin.mauir2r.arm64.fullr2r
Failure [DELETE_FAILED_INTERNAL_ERROR]
adb.exe install -r MauiR2R-android-arm64-fullr2r-Signed.apk
Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE: Scanning Failed.: Package ... could not be assigned a valid UID]
Missing device failure:
List of devices attached
adb.exe wait-for-device
END OF WORK ITEM LOG: Command timed out, and was killed
- 主要语言
- C#
- 星标
- 2.1k
- 派生
- 581
- 平均合并
- 1 天 21 小时
- 30 天内合并 PR
- 241
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
dotnet/android 的其他 Issue
-
Area: App+Library Build
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
Area: Mono.Android
难度 2/5 1-3 小时 新手友好度 65/100
dotnet/android#9192 · 4 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
Area: Mono.Android needs-triage
难度 4/5 3-5 天 新手友好度 30/100
维护者通常 1 天内回复
-
Area: App Runtime needs-triage
难度 4/5 3-5 天 新手友好度 22/100
维护者通常 1 天内回复
-
flaky-ci flaky-tests needs-triage
难度 5/5 一周以上 新手友好度 8/100
维护者通常 1 天内回复
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 85/100
维护者通常 1 天内回复
-
dette technique priorité: basse zone: service
难度 2/5 1-3 小时 新手友好度 68/100
damiensabau/nexus-lobby#25 ·
-
难度 2/5 1-3 小时 新手友好度 78/100
sebastienros/jint#4282 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 76/100
pyrevitlabs/pyRevit#3792 ·
维护者通常 1 天内回复
-
clawsweeper:needs-product-decision clawsweeper:needs-security-review clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:security impact:ux-friction issue-rating: 🦞 diamond lobster P2
难度 2/5 1-3 小时 新手友好度 75/100
openclaw/openclaw-windows-node#1763 · 1 条评论 · 1 个 reaction ·
维护者通常 1 天内回复