Disable GetGeneration test under interpreter (InterpreterIncompatible)

[Copilot]

GC/API/GC/GetGeneration/GetGeneration.dll fails heavily on runtime-interpreter configs: the test expects an object's generation to advance after GC.Collect(), but the interpreter reports the local holding it as pinned, causing the GC to demote it back to generation 0.

Changes

• Set InterpreterIncompatible to true in GetGeneration.csproj to skip the test on interpreter configs until precise local reporting is implemented.

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

[Copilot]

Copilot wasn't able to review any files in this pull request.

[azure-pipelines]

Azure Pipelines:
16 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[azure-pipelines]

Azure Pipelines:
Successfully started running 3 pipeline(s).
13 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

Suppressed comments (1)

src/tests/GC/API/GC/GetGeneration.csproj:5

• Project-level InterpreterIncompatible causes the entire test assembly to exit early via the generated run script, which means Helix/test reporting treats this as “not executed” rather than an explicit xUnit skip. For this test (which already uses xUnit + SkipOnCoreClr), it’s more consistent and discoverable to add a [SkipOnCoreClr(..., RuntimeTestModes.InterpreterActive)] attribute on TestEntryPoint (similar to src/tests/GC/API/GC/Collect.cs) so the skip shows up in test results with a reason, instead of suppressing execution at the harness layer.

    <!-- Interpreter reports locals as pinned, causing generation demotion that this test does not expect -->
    <InterpreterIncompatible>true</InterpreterIncompatible>

[dotnet-policy-service]

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