Skip to content

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

Closed

Description

@github-actions

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1563323
Build error leg or test failing: osx-x64 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) leg of the runtime-coreclr outerloop pipeline (definition 108) fails at the paltests.proj publish step because the Helix SDK cannot find the SYSTEM_ACCESSTOKEN environment variable. All PALTests legs (osx-x64, osx-arm64, linux-x64, linux-arm64, linux_musl-x64, linux_musl-arm64) fail identically, so no PAL tests are ever sent to Helix and the whole pipeline is red on every run in the scanned window.

##[error].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, see: (docs.microsoft.com/redacted) [/__w/1/s/src/coreclr/scripts/paltests.proj]

Build FAILED.
    0 Warning(s)
    1 Error(s)
Build failed with exit code 1. Check errors above.

First build it occurred: persistent across the entire scanned window (builds 1553323 through 1563509, 2026-08-14 .. 2026-08-22); true origin may predate 2026-08-14.

Error Message

{
  "ErrorMessage": [
    "AzurePipelines.props(41,5): error : Azure Pipelines SYSTEM_ACCESSTOKEN variable not found",
    "src/coreclr/scripts/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: 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.

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

Report

Build Repository Step Name Console log Pull Request
1566089 dotnet/runtime Send job to Helix (Unix) Log
1565369 dotnet/runtime Send job to Helix (Unix) Log
1564675 dotnet/runtime Send job to Helix (Unix) Log #131866
1564549 dotnet/runtime Send job to Helix (Unix) Log
1564131 dotnet/runtime Send job to Helix (Unix) Log
1564048 dotnet/runtime Send job to Helix (Unix) Log
1563902 dotnet/runtime Send job to Helix (Unix) Log
1563824 dotnet/runtime Send job to Helix (Unix) Log
1563695 dotnet/runtime Send job to Helix (Unix) Log

Summary

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

Activity

  1. dotnet-policy-service commented on Aug 24, 2026

    @dotnet-policy-service
    Contributor

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

  2. locked and limited conversation to collaborators on Sep 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions