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

[CI] Mac Catalyst CoreData Sections test intermittently hits Earthquakes.sqlite file-sanity error

Aperta
  • Qualcosa non va?
#26,768 2 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
Da chiarire
Stato di attività
Attiva
Stack tecnologico
csharp
Ambito
ci-cd, mobile-dev, testing-qa

Direzione di ricerca

Start with MonoTouchFixtures.CoreData.FetchedResultsControllerTest.Sections and the Mac Catalyst Debug (CoreCLR) Run tests logs from Azure runs 15478073 and 15487532. Investigate how the fixed Caches/Earthquakes.sqlite persistent store reaches the file-sanity check and identify the intermittent writer or filesystem cause. Done means the failure is reproduced or explained and the test no longer intermittently fails, with evidence from the affected simulator job.

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

Descrizione

ci-postmortem copilot

Failure signature

test|MacCatalyst-CoreCLR-Debug|MonoTouchFixtures.CoreData.FetchedResultsControllerTest.Sections|NSPersistentStoreCoordinator.AddPersistentStore|File-unexpectedly-appeared-during-sanity-check|Earthquakes.sqlite

The Mac Catalyst Debug (CoreCLR) FetchedResultsControllerTest.Sections test intermittently fails while adding the fixed Caches/Earthquakes.sqlite persistent store. The CoreData diagnostic is NSCocoaErrorDomain (512), reason "File unexpectedly appeared during sanity check". The underlying writer or filesystem cause is not identified.

Confirmed occurrences

Monitored PR and exact head Azure run / failed job and task Exact test evidence
#26712 ab9ed25ec2bb831eba2d4cefd4a9b2d3c24dbf6f Simulator run 15478073, attempt 1, T: monotouch_maccatalyst / Run tests Mac Catalyst Debug (CoreCLR), NUnit FetchedResultsControllerTest.Sections at 2026-09-26 23:45:16 UTC: NSCocoaErrorDomain (512) and the file-sanity reason above for Earthquakes.sqlite. The identical test passed on an externally initiated stage/job attempt 2 on this unchanged head; the stage and parent run succeeded.
#26711 d6a3a83a67355919db7740a9d2c0b74a00e410de Simulator run 15487532, attempt 1, T: monotouch_maccatalyst / Run tests Mac Catalyst Debug (CoreCLR), execution 594: the same NUnit test, CoreData error code 512, fixed SQLite name and exact file-sanity reason at 2026-09-28 16:59:37 UTC. The Mac Catalyst job failed; other jobs on the parent run were still active when inspected.

First observed: 2026-09-26 23:45:16 UTC. Latest observed: 2026-09-28 16:59:37 UTC. Impact: two confirmed occurrences across two distinct monitored PRs. This fails the Mac Catalyst simulator job. #26711's same job also contains a separate, unresolved Mac Catalyst NativeAOT process exit 139 without a crash report or faulting stack; that crash is not counted as this CoreData signature.

Investigation and classification

The matching Azure TestSummary, nested HtmlReport NUnit XML and per-execution logs on each run establish the exact test, configuration, error code, SQLite filename and CoreData reason. #26712's identical case passed on a subsequent same-head external attempt, proving intermittent test behavior rather than a deterministic assertion for that head. Classification: genuinely flaky test, with an unresolved underlying file writer/filesystem cause; there is no evidence that either PR's source caused it.

All-state issue searches separately covered the stable signature, exact test, CoreData error reason, Earthquakes.sqlite, NSCocoaErrorDomain 512 and the CoreData/coordinator component. The only exact-test candidate, #26227, records a different iOS SpringBoard launch crash; its body and non-ignored comments explicitly treat this CoreData failure as a separate root. No existing issue represents this file-sanity signature.

Workaround and diagnostic limits

An external attempt passed #26712's identical case on the same head; repeating CI is not a proven permanent workaround. No monitor retry was requested: #26711 still has a distinct unresolved NativeAOT crash and an active parent run, and complete accepted-request retry accounting across actors for the 25-PR-lifetime / 10-head limits remains uncertified. The Rolf-authored source branch was not edited. These are direct Azure simulator jobs without Helix work items. Azure TestSummary/HtmlReport artifacts have limited retention; no credentials, machine IPs or worker identities are included.

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

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.