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

[CI] Sonoma Clean bot hangs in simctl delete all for 60 minutes

Aperta
  • Qualcosa non va?
#26,525 8 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
42/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
azure, macos, shell
Ambito
ci-cd, devops, infrastructure

Direzione di ricerca

Esamina clean-bot.sh e i log del bot Azure Clean, iniziando dall'invocazione di simctl delete all su XAMBOT-1024.Sonoma. Ispeziona lo stato di CoreSimulator del worker interessato e determina come il percorso di pulizia possa acquisire diagnostica con limiti definiti prima del timeout. Il lavoro è completato quando la pulizia non occupa più l'agent per 60 minuti, oppure quando il fallimento fornisce diagnostica utilizzabile.

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

Descrizione

ci-postmortem copilot

Summary

The Sonoma Clean bot task has hung in simctl delete all until Azure DevOps terminates the task at its 60-minute timeout in two distinct monitored PRs.

  • Stable signature: X64 Mac Sonoma clean-bot.sh hangs in simctl delete all until the 60-minute Azure task timeout
  • Classification: CI infrastructure failure
  • Distinct monitored PRs: 2
  • Confirmed occurrences: 2
  • First observed timeout: 2026-09-01T18:48:27Z
  • Latest observed timeout: 2026-09-02T03:55:54Z
  • Worker in both occurrences: XAMBOT-1024.Sonoma

Confirmed occurrences

#26475
  • Head: 2ddfa5661d7ae0592ef92481927aa61f28ba8df5
  • Pipeline: xamarin-macios-sim-pr-tests
  • Build 15169876, attempt 1, X64 Mac Sonoma / Clean bot
  • Task interval: 2026-09-01T17:48:17Z–18:48:27Z
  • Minimal signature:
    • + /Applications/Xcode.app/Contents/Developer/usr/bin/simctl delete all
    • The task has timed out.
  • Azure build result: partiallySucceeded.
  • Retry outcome: no cleanup retry was submitted. A separate permitted retry addressed the unrelated FinalizationRaceCondition test failure and passed; the cleanup timeout remained as a nonblocking warning.
#26484
  • Head: fd099f147cffffbce1c6a10b5861f4172fd8117b
  • Pipeline: xamarin-macios-sim-pr-tests
  • Build 15178389, attempt 1, X64 Mac Sonoma / Clean bot
  • Task interval: 2026-09-02T02:55:44Z–03:55:54Z
  • Minimal signature:
    • + /Applications/Xcode.app/Contents/Developer/usr/bin/simctl delete all
    • The task has timed out.
  • Azure build result: partiallySucceeded; all GitHub checks are green.
  • Retry outcome: none. The timeout was nonblocking and no failed test or build job remained to rerun.

Reproduction pattern and impact

Both occurrences used the same job, task identifier, command, operating-system lane, and worker. The command produced no completion output for about 60 minutes and occupied the agent until Azure timed it out. Tests were not invalidated, but the task delayed each pipeline and left the Azure build partially successful.

Investigation performed

The Azure build metadata, timelines, task records, and Clean bot logs were compared directly. The exact command, task timeout text, task duration, and worker match across both PRs. Searches across all open and closed dotnet/macios issues used the exact command, task name, timeout text, worker, script name, and simulator-cleanup terms. The only candidates were #6740, an unrelated Xcode UI synchronization report, and #26385, an unrelated checkout/credential failure.

A binlog, TestSummary, HtmlReport, or crash report is not applicable because this is a shell-based post-test simulator cleanup hang rather than a build, test assertion, or process crash.

Current diagnosis and workaround

This is a worker-specific CoreSimulator cleanup infrastructure failure. No source workaround is known. The affected worker's CoreSimulator state should be inspected or reset, and the cleanup path should capture bounded diagnostics before timing out so future hangs identify the blocking simulator service or process.

Azure logs are retention-limited.

Lingua principale
C#
Stelle
2.9k
Fork
578
Merge medio
2g 12h
PR unite (30g)
189

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

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/macios

Tutte le issue di dotnet/macios

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.