Skip to content

Failed test: GC/API/GC/GetGeneration/GetGeneration.dll #131542

Description

@JulieLeeMSFT

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

  • Massive failures in many configs
14:46:12.949 Running test: GC/API/GC/GetGeneration/GetGeneration.dll
0 0
ObjectTest Failed!
0 0
arrayTest Failed!
failTest Passed!

Test for GetGeneration() FAILED!
Xunit.Sdk.EqualException: Assert.Equal() Failure: Values differ
Expected: 100
Actual:   1
   at Xunit.Assert.Equal[T](T expected, T actual, IEqualityComparer`1 comparer) in /_/src/arcade/src/Microsoft.DotNet.XUnitAssert/src/EqualityAsserts.cs:line 102
   at Xunit.Assert.Equal[T](T expected, T actual) in /_/src/arcade/src/Microsoft.DotNet.XUnitAssert/src/EqualityAsserts.cs:line 36
   at Program.<<Main>$>g__TestExecutor28|0_29(StreamWriter tempLogSw, StreamWriter statsCsvSw, <>c__DisplayClass0_0&)

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

Build Repository Test Pull Request
1538649 dotnet/runtime GC/API/GC/GetGeneration/GetGeneration.dll #131754
1537295 dotnet/runtime GC/API/GC/GetGeneration/GetGeneration.dll
1536715 dotnet/runtime GC/API/GC/GetGeneration/GetGeneration.dll
1534710 dotnet/runtime GC/API/GC/GetGeneration/GetGeneration.dll
1533324 dotnet/runtime GC/API/GC/GetGeneration/GetGeneration.dll
1533254 dotnet/runtime GC/API/GC/GetGeneration/GetGeneration.dll #131590
1532391 dotnet/runtime GC/API/GC/GetGeneration/GetGeneration.dll #131027
1531411 dotnet/runtime GC/API/GC/GetGeneration/GetGeneration.dll

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
2 8 8

Activity

  1. added
    area-CodeGen-coreclrCLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI
    on Jul 29, 2026
  2. dotnet-policy-service commented on Jul 29, 2026

    @dotnet-policy-service
    Contributor

    Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
    See info in area-owners.md if you want to be subscribed.

  3. JulieLeeMSFT commented on Jul 29, 2026

    @JulieLeeMSFT
    MemberAuthor

    GC tests are failing in runtime-interpreter. cc @davidwrighton, if it's related to your recent change.

  4. dotnet-policy-service commented on Jul 29, 2026

    @dotnet-policy-service
    Contributor

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

  5. janvorli commented on Jul 29, 2026

    @janvorli
    Member

    This test has been always failing on my local machine. I am actually surprised it wasn't failing in the CI bewfore.

  6. added
    blocking-outerloopBlocking the 'runtime-coreclr outerloop' and 'runtime-libraries-coreclr outerloop' runs
    and removed
    blocking-outerloopBlocking the 'runtime-coreclr outerloop' and 'runtime-libraries-coreclr outerloop' runs
    on Jul 30, 2026
  7. janvorli commented on Jul 30, 2026

    @janvorli
    Member

    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.

  8. janvorli commented on Jul 31, 2026

    @janvorli
    Member

    I'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.

  9. 1 remaining item

  10. removed
    untriagedNew issue has not been triaged by the area owner
    on Aug 3, 2026
  11. added this to the 12.0.0 milestone on Aug 3, 2026
  12. dotnet-policy-service commented on Aug 3, 2026

    @dotnet-policy-service
    Contributor

    Tagging subscribers to this area: @JulieLeeMSFT, @BrzVlad, @janvorli
    See info in area-owners.md if you want to be subscribed.

  13. janvorli commented on Aug 3, 2026

    @janvorli
    Member

    Right.

  14. JulieLeeMSFT commented on Aug 4, 2026

    @JulieLeeMSFT
    MemberAuthor

    @BrzVlad, @janvorli, this test is failing heavily. I see that the fix is planned for .NET 12. Meanwhile, can you please disable the test?

  15. BrzVlad commented on Aug 4, 2026

    @BrzVlad
    Member

    @copilot Disable this test via InterpreterIncompatible

  16. added a commit that references this issue on Aug 5, 2026
    c8f9797
  17. locked and limited conversation to collaborators on Sep 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

  • Status
    No status

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions