[ci-scan] Build break: PALTests Send job to Helix fails with SYSTEM_ACCESSTOKEN variable not found

[github-actions]

Build Information

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

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 Send job to Helix (Unix) step for the PALTests legs (linux-x64, osx-x64, osx-arm64, linux_musl-x64, linux_musl-arm64, linux-arm64) fails during the Helix SDK restore because the AzDO System.AccessToken variable is not exposed to the step. The Helix SDK's AzurePipelines.props aborts and the paltests.proj build fails:

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 ... [/src/coreclr/scripts/paltests.proj]
Build FAILED.
    1 Error(s)
Build failed with exit code 1. Check errors above.

Persistent across the entire scanned window (present in builds 1558864, 1559609, 1560451, 1561111, 1561604, source 1561949, and follow-up 1562816); true origin may predate 2026-08-19. This is a step configuration break in the PALTests Send job to Helix task, not a product test failure.

Error Message

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

Agentic workflow metadata (ci-failure-scan)

Workflow artifact: ci-failure-scan
Artifact kind: kbe-verification
Verified match count: 3 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.

Note

This issue was generated by an AI agent (ci-failure-scan GitHub Copilot workflow).

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

Report

Build	Repository	Step Name	Console log	Pull Request
1563824	dotnet/runtime	Send job to Helix (Unix)	Log
1563695	dotnet/runtime	Send job to Helix (Unix)	Log
1563509	dotnet/runtime	Send job to Helix (Unix)	Log
1563323	dotnet/runtime	Send job to Helix (Unix)	Log

Summary

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