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

Đang mở
#137,367 1 bình luận 0 reaction 0 người được giao Xem trên GitHub

Maintainer thường phản hồi trong vòng 1 ngày

Chưa có ai nhận issue này.

Đánh giá

Độ khó
4/5
Thời gian dự kiến
3-5 ngày
Mức phù hợp với người mới
35/100
Loại issue
Lỗi
Độ rõ ràng
Khá rõ ràng
Mức độ hoạt động
Sôi nổi
Công nghệ
github-actions, javascript, node.js
Lĩnh vực
ci-cd, devops

Hướng nghiên cứu

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.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.

Mô tả

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
Ngôn ngữ chính
C#
Star
18.4k
Fork
5.8k
Merge trung bình
2 ngày 19 giờ
Pull request đã merge (30 ngày)
590

Chuẩn bị môi trường

Mở trong Codespaces

Khởi chạy dev container của dự án ngay trên trình duyệt, bằng tài khoản GitHub của bạn.

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Issue khác của dotnet/runtime

Tất cả issue của dotnet/runtime

Issue tương tự

Thêm issue về C#

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.