[ci-scan] Build break: PALTests Send to Helix fails with SYSTEM_ACCESSTOKEN variable not found on runtime-coreclr outerloop

[github-actions]

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1560135
Build error leg or test failing: linux-arm64 / linux-x64 / osx-arm64 / osx-x64 / linux_musl-* Debug PALTests - Send job to Helix (Unix) (paltests.proj)

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.

Error Details

Every Debug PALTests leg of runtime-coreclr outerloop (definition 108) fails at the Send job to Helix (Unix) step. The Helix SDK's AzurePipelines.props cannot find SYSTEM_ACCESSTOKEN, so paltests.proj never sends the Helix job and the leg errors out before any test runs:

/__w/1/s/.packages/microsoft.dotnet.helix.sdk/11.0.0-beta.26411.119/tools/azure-pipelines/AzurePipelines.props(41,5): error : Azure Pipelines SYSTEM_ACCESSTOKEN variable not found. Either the build is not running in Azure Pipelines, or the current step is not configured correctly. Please configure this step with the System.AccessToken variable ... [/__w/1/s/src/coreclr/scripts/paltests.proj]

The failure is persistent: it reproduces across the entire scanned build window (builds 1560135, 1559609, 1558864, 1556858 all show it) and in the follow-up build 1560451, affecting all PALTests architectures. True origin likely predates the scanned window.

Error Message

{
  "ErrorMessage": [
    "error : Azure Pipelines SYSTEM_ACCESSTOKEN variable not found.",
    "paltests.proj]"
  ],
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Agentic workflow metadata (ci-failure-scan)

Workflow artifact: ci-failure-scan
Artifact kind: kbe-verification
Verified match count: 2 hits in failure.log

---

Filed by ci-failure-scan (detection only). ci-failure-fix walks open [ci-scan] KBEs and either opens a small fix PR or comments here to loop in owners — it never disables the test.

Generated by CI Outer-Loop Failure Scanner · opus48 · 496.5 AIC · ⌖ 18.1 AIC · ⊞ 20.7K · ◷

Report

Build	Repository	Step Name	Console log	Pull Request
1561111	dotnet/runtime	Send job to Helix (Unix)	Log

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
1	1	1

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.