Disable GetGeneration test under interpreter (InterpreterIncompatible) by Copilot · Pull Request #131816 · dotnet/runtime

Copilot · 2026-08-04T16:45:48Z

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.

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

Copilot

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

azure-pipelines · 2026-08-04T16:46:03Z

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.

Co-authored-by: BrzVlad <4720621+BrzVlad@users.noreply.github.com>

azure-pipelines · 2026-08-04T16:52:50Z

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 · 2026-08-04T16:53:59Z

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

BrzVlad · 2026-08-05T06:23:01Z

/ba-g pr just disables a test

Copilot · 2026-08-04T16:45:48Z

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.

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

Copilot

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

azure-pipelines · 2026-08-04T16:46:03Z

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.

Co-authored-by: BrzVlad <4720621+BrzVlad@users.noreply.github.com>

azure-pipelines · 2026-08-04T16:52:50Z

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 · 2026-08-04T16:53:59Z

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

BrzVlad · 2026-08-05T06:23:01Z

/ba-g pr just disables a test

Copilot · 2026-08-04T16:45:48Z

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.

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

Copilot

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

azure-pipelines · 2026-08-04T16:46:03Z

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.

Co-authored-by: BrzVlad <4720621+BrzVlad@users.noreply.github.com>

azure-pipelines · 2026-08-04T16:52:50Z

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 · 2026-08-04T16:53:59Z

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

BrzVlad · 2026-08-05T06:23:01Z

/ba-g pr just disables a test

Copilot · 2026-08-04T16:45:48Z

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.

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

Copilot

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

azure-pipelines · 2026-08-04T16:46:03Z

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.

Co-authored-by: BrzVlad <4720621+BrzVlad@users.noreply.github.com>

azure-pipelines · 2026-08-04T16:52:50Z

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 · 2026-08-04T16:53:59Z

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

BrzVlad · 2026-08-05T06:23:01Z

/ba-g pr just disables a test

Copilot · 2026-08-04T16:45:48Z

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.

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

Copilot

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

azure-pipelines · 2026-08-04T16:46:03Z

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.

Co-authored-by: BrzVlad <4720621+BrzVlad@users.noreply.github.com>

azure-pipelines · 2026-08-04T16:52:50Z

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 · 2026-08-04T16:53:59Z

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

BrzVlad · 2026-08-05T06:23:01Z

/ba-g pr just disables a test

Copilot · 2026-08-04T16:45:48Z

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.

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

Copilot

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

azure-pipelines · 2026-08-04T16:46:03Z

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.

Co-authored-by: BrzVlad <4720621+BrzVlad@users.noreply.github.com>

azure-pipelines · 2026-08-04T16:52:50Z

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 · 2026-08-04T16:53:59Z

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

BrzVlad · 2026-08-05T06:23:01Z

/ba-g pr just disables a test

Copilot · 2026-08-04T16:45:48Z

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.

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

Copilot

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

azure-pipelines · 2026-08-04T16:46:03Z

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.

Co-authored-by: BrzVlad <4720621+BrzVlad@users.noreply.github.com>

azure-pipelines · 2026-08-04T16:52:50Z

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 · 2026-08-04T16:53:59Z

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

BrzVlad · 2026-08-05T06:23:01Z

/ba-g pr just disables a test

Copilot · 2026-08-04T16:45:48Z

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.

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

Copilot

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

azure-pipelines · 2026-08-04T16:46:03Z

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.

Co-authored-by: BrzVlad <4720621+BrzVlad@users.noreply.github.com>

azure-pipelines · 2026-08-04T16:52:50Z

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 · 2026-08-04T16:53:59Z

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

BrzVlad · 2026-08-05T06:23:01Z

/ba-g pr just disables a test

Initial plan
89671dd

CopilotAI self-assigned this Aug 4, 2026

CopilotAI review requested due to automatic review settings August 4, 2026 16:45

CopilotAI assigned BrzVlad Aug 4, 2026

CopilotAI reviewed Aug 4, 2026
View reviewed changes

CopilotAI linked an issue Aug 4, 2026 that may be closed by this pull request
Failed test: GC/API/GC/GetGeneration/GetGeneration.dll #131542
Closed

Copilotstarted work on behalf of BrzVlad August 4, 2026 16:46 View session

Disable GetGeneration test on interpreter
559bdde
Co-authored-by: BrzVlad <4720621+BrzVlad@users.noreply.github.com>

CopilotAI review requested due to automatic review settings August 4, 2026 16:49

Copilotstarted reviewing on behalf of BrzVlad August 4, 2026 16:50 View session

BrzVlad marked this pull request as ready for review August 4, 2026 16:52

BrzVlad added the area-CodeGen-Interpreter-coreclr label Aug 4, 2026

BrzVlad approved these changes Aug 4, 2026
View reviewed changes

CopilotAI reviewed Aug 4, 2026
View reviewed changes

davidwrighton approved these changes Aug 4, 2026
View reviewed changes

janvorli approved these changes Aug 4, 2026
View reviewed changes

CopilotAI changed the title ~~[WIP] Fix failed test for GetGeneration in GC API~~Disable GetGeneration test under interpreter (InterpreterIncompatible)Aug 4, 2026

Copilotfinished work on behalf of BrzVlad August 4, 2026 17:02

CopilotAI requested a review from BrzVlad August 4, 2026 17:02

build-analysisBot mentioned this pull request Aug 4, 2026
The Operation will be canceled. The next steps may not contain expected logs. dotnet/dnceng#3008
Open
3 tasks

BrzVlad merged commit c8f9797 into mainAug 5, 2026
87 of 95 checks passed

BrzVlad deleted the copilot/fix-failed-getgeneration-test branch August 5, 2026 06:23

github-actionsBot mentioned this pull request Aug 6, 2026
[ci-scan] Test failure: GC/API/GC/GetGeneration/GetGeneration.dll fails under interpreter (post-fix recurrence) #131914
Closed

dotnet-maestroBot mentioned this pull request Aug 6, 2026
[main] Source code updates from dotnet/runtime dotnet/dotnet#8163
Merged

CopilotAI mentioned this pull request Aug 6, 2026
Fix GetGeneration GC API test failure under interpreter #131918
Merged
5 tasks

dotnet-milestone-botBot added this to the 11.0-rc1 milestone Aug 6, 2026