Linux arm64 single-file CI failures caused by inconsistent .NET 11 host package restore

Aperta
  • Qualcosa non va?
#6,213 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
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
azure, csharp
Ambito
ci-cd, devtools, testing

Direzione di ricerca

Start by comparing the CI logs and binlogs for builds 1674595 and 1674668, then inspect NuGet.config and the single-file test targets that restore Microsoft.NETCore.App.Host.linux-arm64. Trace how package source selection affects the host package and the DBI identity used by the DbgShim and SOS tests. Done means Linux arm64 .NET 11 single-file tests use a host and test runtime components from a consistent build, with CI confirming the fix.

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

Descrizione

Description

Linux arm64 CI is failing for .NET 11 single-file targets in:

  • Microsoft.Diagnostics.DbgShimTests.CreateDebuggingInterfaceFromVersion3LoadPolicy
  • SOS.Tests.ClrStackFrameCountTests.ClrStack_ICorDebugFrameCount, running clrstack -i

The passing and failing builds restored different contents for Microsoft.NETCore.App.Host.linux-arm64, despite requesting the same 11.0.0 version.

Evidence

Build Queued, UTC Host package source
1674595, Linux arm64 passing November 11, 03:06 darc-pub-dotnet-dotnet-a586537b-1
1674668, first observed failure November 11, 05:08 dotnet-public

Both restored Microsoft.NETCore.App.Runtime.linux-arm64 11.0.0 from the pinned Darc feed. The host package content hashes differ between builds.

The binlogs confirm that OverrideTestingVersions executes, ResolveAppHosts requests exactly [11.0.0], and single-file publishing consumes the restored host. The override is not being skipped. However, NuGet.config permits both feeds without package source mapping, so the version constraint does not identify a unique build.

The failing single-file target requests DBI build ID 53f2b051911c0e4fdc667d2615853c36052740f9, which does not match the supplied DBI. The DbgShim provider rejects that mismatch. SOS records the same requested DBI identity and reports:

clrstack -i is unsupported on this target.
The ICorDebug interface cannot be constructed.

No repository SDK/runtime pin changed between these builds. The installed runtime remains pinned to 11.0.0-rtm.26514.118.

Expected behavior

Single-file hosts and the runtime/DAC/DBI supplied for testing should come from a consistent runtime build. Restore should enforce package provenance or content identity, rather than relying solely on the shared 11.0.0 version.

Verified by CI log, binlog, and package inspection; no local execution repro. The exact reason restore selected different feeds, and the precise SOS activation failure, remain unconfirmed.

Lingua principale
C++
Stelle
1.3k
Fork
407
Merge medio
21h 5m
PR unite (30g)
78

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

  • Nessun Dockerfile né file Docker Compose
  • Nessun 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/diagnostics

Tutte le issue di dotnet/diagnostics

Issue simili

Altre issue su C++

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.