Repository navigation
Failed test: GC/API/GC/GetGeneration/GetGeneration.dll #131542
Description
Activity
- addedKnown Build ErrorUse this to report build issues in the .NET Helix tabUse this to report build issues in the .NET Helix tab
on Jul 29, 2026 - addeduntriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner
on Jul 29, 2026 - addedarea-CodeGen-coreclrCLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMICLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI
on Jul 29, 2026 dotnet-policy-service commented
on Jul 29, 2026 ContributorMore actionsTagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.GC tests are failing in runtime-interpreter. cc @davidwrighton, if it's related to your recent change.
- addedblocking-clean-ci-optionalBlocking optional rolling runsBlocking optional rolling runsand removedarea-CodeGen-coreclrCLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMICLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI
on Jul 29, 2026 dotnet-policy-service commented
on Jul 29, 2026 ContributorMore actionsTagging subscribers to this area: @anicka-net, @dotnet/gc
See info in area-owners.md if you want to be subscribed.This test has been always failing on my local machine. I am actually surprised it wasn't failing in the CI bewfore.
Reacted by Julie Lee- addedblocking-outerloopBlocking the 'runtime-coreclr outerloop' and 'runtime-libraries-coreclr outerloop' runsBlocking the 'runtime-coreclr outerloop' and 'runtime-libraries-coreclr outerloop' runsand removedblocking-outerloopBlocking the 'runtime-coreclr outerloop' and 'runtime-libraries-coreclr outerloop' runsBlocking the 'runtime-coreclr outerloop' and 'runtime-libraries-coreclr outerloop' runs
on Jul 30, 2026 The test expects that a generation of a freshly created object will grow after GC.Collect() call and with interpreter it doesn't. I have verified that the local holding the object is reported to GC. It is reported as pinned, so I guess that might cause a demotion. I am looking into it to make sure it is not a bug.
Reacted by Julie LeeI've debugged it. It is an interpreter incompatibility. The thing is that when interpreted code reports the local that we check the generation for, the GC info marks that local intentionally as pinned. GC then due to this decides to demote the object back to generation 0. But the test expects that after a GC.Collect, it would get higher generation.
1 remaining item
- removeduntriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner
on Aug 3, 2026 dotnet-policy-service commented
on Aug 3, 2026 ContributorMore actionsTagging subscribers to this area: @JulieLeeMSFT, @BrzVlad, @janvorli
See info in area-owners.md if you want to be subscribed.Right.
- marked [ci-scan] Test failure: GC/API/GC/GetGeneration/GetGeneration.dll fails under interpreter on osx-arm64 #131743 as a duplicate of this issue
on Aug 3, 2026 @copilot Disable this test via
InterpreterIncompatible- linked a pull request that will close this issueDisable GetGeneration test under interpreter (InterpreterIncompatible) #131816
on Aug 4, 2026 - added a commit that references this issue
on Aug 5, 2026 - locked and limited conversation to collaborators
on Sep 4, 2026
Metadata
Metadata
Labels
Type
Projects
- StatusShow more project fieldsNo status
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1531411
Build error leg or test failing: GC/API/GC/GetGeneration/GetGeneration.dll
Error Message
Fill the error message using step by step known issues guidance.
{ "ErrorMessage": "Failed test: GC/API/GC/GetGeneration/GetGeneration.dll", "BuildRetry": false, "ExcludeConsoleLog": false }Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1531411
Error message validated:
[Failed test: GC/API/GC/GetGeneration/GetGeneration.dll]Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 7/29/2026 5:40:38 PM UTC
Report
Summary