Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1558864
Build error leg or test failing: PALTests (osx-arm64/osx-x64/linux-x64/linux-arm64/linux_musl-x64/linux_musl-arm64 Debug) - 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
All six Unix PALTests legs of runtime-coreclr outerloop (definition 108) fail at the Send job to Helix (Unix) step, before any Helix work item is queued. The paltests.proj MSBuild invocation aborts because the Helix SDK cannot read the Azure Pipelines access-token variable:
.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),batch#systemaccesstoken [/src/coreclr/scripts/paltests.proj]
Observed on builds 1556858, 1558516, 1558864, and follow-up 1559609 (3 hits per leg); absent on build 1555339. The failure reproduces on every Unix PALTests leg and persists across builds, so it is a stable configuration break rather than transient infra noise.
Error Message
{
"ErrorMessage": "Azure Pipelines SYSTEM_ACCESSTOKEN variable not found. Either the build is not running in Azure Pipelines, or the current step is not configured correctly.",
"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
Generated by CI Outer-Loop Failure Scanner · opus48 · 501 AIC · ⌖ 17.4 AIC · ⊞ 20.7K · ◷
Report
| Build |
Repository |
Step Name |
Console log |
Pull Request |
| 1561111 |
dotnet/runtime |
Send job to Helix (Unix) |
Log |
|
| 1560451 |
dotnet/runtime |
Send job to Helix (Unix) |
Log |
|
| 1560135 |
dotnet/runtime |
Send job to Helix (Unix) |
Log |
|
Summary
| 24-Hour Hit Count |
7-Day Hit Count |
1-Month Count |
| 3 |
3 |
3 |
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1558864
Build error leg or test failing: PALTests (osx-arm64/osx-x64/linux-x64/linux-arm64/linux_musl-x64/linux_musl-arm64 Debug) - Send job to Helix (Unix)
KBE authoring guidance (ci-failure-scan)
Error Detailsis for readers. Paste the full exception, stack trace, or build error excerpt so the failure is understandable without opening the raw log.Error Message.ErrorMessageis a case-sensitive ordinalString.Containssubstring copied verbatim from the failing log.BuildRetrytotrueonly for a clear infrastructure retry case.ExcludeConsoleLogdisables Helix console-log scanning.Error Details
All six Unix
PALTestslegs ofruntime-coreclr outerloop(definition 108) fail at theSend job to Helix (Unix)step, before any Helix work item is queued. Thepaltests.projMSBuild invocation aborts because the Helix SDK cannot read the Azure Pipelines access-token variable:Observed on builds 1556858, 1558516, 1558864, and follow-up 1559609 (3 hits per leg); absent on build 1555339. The failure reproduces on every Unix PALTests leg and persists across builds, so it is a stable configuration break rather than transient infra noise.
Error Message
{ "ErrorMessage": "Azure Pipelines SYSTEM_ACCESSTOKEN variable not found. Either the build is not running in Azure Pipelines, or the current step is not configured correctly.", "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
Report
Summary