Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

CI: MAUI R2R Helix device-lab failures across Android queues

Aperta
  • Qualcosa non va?
#12,658 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
android
Ambito
ci-cd, mobile-dev, testing

Direzione di ricerca

Inizia rieseguendo la pipeline pubblica della PR di dotnet-android e ispeziona la console del work-item Helix collegata per l'attività MAUI R2R. Confronta le assegnazioni di host e dispositivi con le firme dei log relative all'autorizzazione, al gestore dei pacchetti e ai dispositivi mancanti. L'attività è completata quando i dispositivi interessati sono autorizzati e disponibili, lo stato del relativo gestore dei pacchetti è integro e le esecuzioni ripetute hanno esito positivo in entrambe le code Android.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

flaky-ci needs-triage
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 27091JEGR21946 on DNCENGWIN-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
Lingua principale
C#
Stelle
2.1k
Fork
581
Merge medio
2g 33m
PR unite (30g)
204

Preparare l'ambiente

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di dotnet/android

Tutte le issue di dotnet/android

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.