[ci-scan] Build break: Component Detection JavaScript SyntaxError on macOS

Aperta
  • Qualcosa non va?
#137,367 1 commento 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
github-actions, javascript, node.js
Ambito
ci-cd, devops

Direzione di ricerca

Start with the linked PR build and raw task log to confirm the malformed line in Component Governance Detection version 0.2621105.1. The issue does not identify a source file or establish whether the bundle or worker caused the corruption, so tracing the task distribution and macOS arm64 execution path is needed. Done means identifying and resolving the cause so the injected task parses and runs successfully.

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

Descrizione

area-Infrastructure blocking-clean-ci Known Build Error untriaged
Description

The policy-injected Component Governance Detection task fails while parsing its own JavaScript bundle on the macOS arm64 innerloop leg. The failing bundle contains an invalid assignment with 9 where an assignment operator would be expected. Whether this originated in the task distribution or worker-local corruption has not been established.

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1675632
Build error leg or test failing: Build / osx-arm64 release CoreLib_Libraries_AnalyzersLinker - Component Detection (auto-injected by policy)
Pull request: https://github.com/dotnet/runtime/pull/136983
Raw task log: https://dev.azure.com/dnceng-public/public/_apis/build/builds/1675632/logs/157

KBE authoring guidance (ci-failure-scan)
  • Error Details is for readers. Paste the full exception, stack trace, or build error excerpt so the failure is understandable without opening the raw log.
  • Build Analysis parses only the single JSON block under Error Message.
  • ErrorMessage is a case-sensitive ordinal String.Contains substring copied verbatim from the failing log.
  • Set BuildRetry to true only for a clear infrastructure retry case. ExcludeConsoleLog disables Helix console-log scanning.
Reproduction Steps

Observed in the linked PR build's Component Detection task, version 0.2621105.1. Inspect the linked raw task log. No standalone reproduction or CI retry was performed.

Expected behavior

The injected task should successfully parse its JavaScript bundle and run component detection.

Actual behavior

The task terminates before component detection can run, failing the job and Build Analysis.

Error Details

[Host] Selected Node version: Node20 (Strategy: Node20Strategy)
ComponentGovernanceComponentDetection_f2f0881f-4b99-4a1c-80ea-f5b13fd6cec4/0.2621105.1/index.js:12722
var SEMRESATTRS_K8S_DAEMONSET_UID 9 TMP_K8S_DAEMONSET_UID;
                                  ^

SyntaxError: Unexpected number
    at wrapSafe (node:internal/modules/cjs/loader:1464:18)
    at Module._compile (node:internal/modules/cjs/loader:1495:20)
    at Module._extensions..js (node:internal/modules/cjs/loader:1623:10)
    at Module.load (node:internal/modules/cjs/loader:1266:32)
    at Module._load (node:internal/modules/cjs/loader:1091:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:164:12)
    at node:internal/main/run_main_module:28:49

Node.js v20.20.2

Error Message

{
  "ErrorMessage": "var SEMRESATTRS_K8S_DAEMONSET_UID 9 TMP_K8S_DAEMONSET_UID;",
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}
Agentic workflow metadata (ci-failure-scan)

Workflow artifact: agent-merge (shared ci-failure-scan KBE verification)
Artifact kind: kbe-verification
Verified match count: 1 hits in failure.log

Regression?

Unknown. The failure is in the injected task's JavaScript, not a component-detection implementation changed by the linked PR. This report does not establish a faulty upstream task release or a particular worker/cache cause.

Known Workarounds

None verified. No policy bypass, task suppression, or CI rerun was used.

Configuration
  • Pipeline: runtime-dev-innerloop.
  • Leg: osx-arm64 release CoreLib_Libraries_AnalyzersLinker.
  • Component Governance Detection: 0.2621105.1.
  • Node.js: v20.20.2.
  • Impact on other operating systems and architectures is unknown.
Other information

Open and recently closed runtime/dnceng issue searches found no matching scanner syntax-error report. Searches for open or recently merged scanner fixes also found no matching PR. The exact malformed JavaScript line matches the failing task log once and matches no passing/skipped lines.

Generated by Copilot

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1675632
Error message validated: [var SEMRESATTRS_K8S_DAEMONSET_UID 9 TMP_K8S_DAEMONSET_UID;]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 11/11/2026 5:42:55 PM UTC

Report
Build Repository Step Name Console log Pull Request
1675632 dotnet/runtime Component Detection (auto-injected by policy) Log dotnet/runtime#136983
Summary
24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 1 1
Lingua principale
C#
Stelle
18.4k
Fork
5.8k
Merge medio
2g 19h
PR unite (30g)
590

Preparare l'ambiente

Apri in Codespaces

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

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

Tutte le issue di dotnet/runtime

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.