[ci-scan] Test failure: GC/API/GC/GetConfigurationVariables on GCStandAlone windows-arm64 #131318

Activity

1. github-actions

   added

   blocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'

   Known Build ErrorUse this to report build issues in the .NET Helix tabUse this to report build issues in the .NET Helix tab

   agentic-workflows

   on Jul 24, 2026
2. dotnet-policy-service

   added

   untriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner

   on Jul 24, 2026
3. VincentBu commented on Jul 28, 2026

   

   VincentBu

   on Jul 28, 2026

   Contributor

   More actions

   Failed in: gc-standalone 20260726.1

   Failed tests:

   coreclr windows arm64 Checked gcstandaloneserver @ Windows.11.Arm64.Open
   - GC/API/GC/GetConfigurationVariables/GetConfigurationVariables.cmd
   coreclr windows x64 Checked gcstandaloneserver @ Windows.10.Amd64.Open
   - GC/API/GC/GetConfigurationVariables/GetConfigurationVariables.cmd
   
   

   Error message:

   
   Return code:      1
   Raw output file:      C:hwAAEB0999w9E130886uploadsAPIGCGetConfigurationVariablesoutput.txt
   Raw output:
   BEGIN EXECUTION
    "C:hwAAEB0999pcorerun.exe" -p "System.Reflection.Metadata.MetadataUpdater.IsSupported=false" -p "System.Runtime.Serialization.EnableUnsafeBinaryFormatterSerialization=true"  GetConfigurationVariables.dll 
   Expected: 100
   Actual: 3
   END EXECUTION - FAILED
   FAILED
   Test Harness Exitcode is : 1
   To run the test:
   Set up CORE_ROOT and run.
   > C:hwAAEB0999w9E130886eGCGC../API/GC/GetConfigurationVariables/GetConfigurationVariables.cmd
   

   Stack trace:

      at Xunit.Assert.True(Nullable`1 condition, String userMessage) in /_/src/arcade/src/Microsoft.DotNet.XUnitAssert/src/BooleanAsserts.cs:line 135
      at Program.<<Main>$>g__TestExecutor29|0_30(StreamWriter tempLogSw, StreamWriter statsCsvSw, <>c__DisplayClass0_0&)
   
4. kotlarmilos

   added this to the 12.0.0 milestone on Jul 28, 2026
5. kotlarmilos

   added

   area-GC-coreclr

   on Jul 28, 2026
6. github-project-automation

   added this to AppModelon Jul 28, 2026
7. dotnet-policy-service commented on Jul 28, 2026

   

   dotnet-policy-servicebot

   on Jul 28, 2026 – with Dotnet Policy Service

   Contributor

   More actions

   Tagging subscribers to this area: @anicka-net, @dotnet/gc
   See info in area-owners.md if you want to be subscribed.
8. dotnet-policy-service

   removed

   untriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner

   on Jul 28, 2026
9. github-actions commented on Jul 29, 2026

   

   github-actionsbot

   on Jul 29, 2026 – with GitHub Actions

   ContributorAuthor

   More actions

   Workflow artifact: ci-fix
   Artifact kind: handoff
   Linked KBE: #131318

   Note

   AI/Copilot-generated triage note.

   This Known Build Error has no producible automated code change (reason: standalone-GC runtime behavior — a GC-configuration/runtime code path that must not be auto-patched), so I could not open even a best-effort PR. Looping in owners so it can be fixed forward rather than muted.

   Root cause (best analysis)

   GC/API/GC/GetConfigurationVariables/GetConfigurationVariables.cmd fails only on the GCStandAlone / GCStandAloneServer legs (windows-arm64 checked), returning Actual: 3 instead of the expected 100 (pass):

   Running test: GC/API/GC/GetConfigurationVariables/GetConfigurationVariables.cmd
   Expected: 100
   Actual: 3
   

   The test enumerates GC configuration variables via GCConfig/GC.GetConfigurationVariables(). Under the standalone GC the returned configuration set differs from the built-in GC, so an assertion in the test fails and the process returns a non-100 exit code. This is either (a) a standalone-GC gap where a configuration variable is not surfaced, or (b) a test expectation that does not account for the standalone-GC configuration surface. Related closed predecessor on a different leg: #130289.

   Evidence

   • Failing build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1519705
   • First build it occurred: computed within the scanned window (build 1519705); may not be the true origin.
   • Possible related PR: none identified with sufficient confidence.

   Suggested reviewers / area contacts

   • Likely author: none identified with sufficient confidence.
   • Area owners (area-GC-coreclr): @anicka-net, @dotnet/gc

   A fix would likely either surface the missing configuration variable(s) through the standalone-GC path or adjust the test's expected configuration set to be standalone-GC aware.

   Warning

   Firewall blocked 1 domain

   The following domain was blocked by the firewall during workflow execution:

   • awmgmcpg

   To allow these domains, add them to the network.allowed list in your workflow frontmatter:

   network:
     allowed:
       - defaults
       - "awmgmcpg"

   See Network Configuration for more information.

   Generated by CI Outer-Loop Failure Fixer · 396.3 AIC · ⌖ 17.9 AIC · ⊞ 17.1K · ◷