Fix SuppressGCTransitionNegativeTest: restore GCStressIncompatible, document CLRTestExitCode requirement by Copilot · Pull Request #131670 · dotnet/runtime

Copilot · 2026-07-31T19:28:13Z

SuppressGCTransitionNegativeTest was failing under GC stress with Expected: -2146233082 / Actual: 100. PR #126108 replaced <GCStressIncompatible>true</GCStressIncompatible> with [SkipOnCoreClr(..., RuntimeTestModes.AnyGCStress)], but this test has a non-default CLRTestExitCode (crash exit code). An XUnit-level skip returns 100, which conflicts with the expected crash exit code the harness checks.

SuppressGCTransitionNegativeTest.csproj: Restore <GCStressIncompatible>true</GCStressIncompatible> so GC stress skipping happens at the wrapper-script level, not inside XUnit.
SuppressGCTransitionNegativeTest.cs: Remove the [SkipOnCoreClr] attribute that caused the XUnit-level skip.
requiresprocessisolation.md: Add Rule 30 — tests with a non-default CLRTestExitCode must use process-level skip mechanisms (e.g., GCStressIncompatible) rather than XUnit-level attributes; also add CLRTestExitCode to the summary table.

Note

This description was generated with AI assistance.

FixesFailed test: Interop/SuppressGCTransition/SuppressGCTransitionNegativeTest/SuppressGCTransitionNegativeTest #131667

Copilot

Copilot was unable to review this pull request because there is no eligible user to bill. To allow Copilot reviews on bot-authored pull requests, enable direct organization billing in your organization's Copilot settings.

azure-pipelines · 2026-07-31T19:28:32Z

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.

…d of SkipOnCoreClr The test sets CLRTestExitCode to a crash exit code, so an XUnit-level skip (which returns 100) conflicts with the expected exit code. Use the process-level GCStressIncompatible mechanism instead. Also document this requirement in requiresprocessisolation.md. Fixes#131667 Co-authored-by: jkoritzinsky <1571408+jkoritzinsky@users.noreply.github.com>

Copilot

Copilot was unable to review this pull request because there is no eligible user to bill. To allow Copilot reviews on bot-authored pull requests, enable direct organization billing in your organization's Copilot settings.

dotnet-policy-service · 2026-07-31T19:35:33Z

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

azure-pipelines · 2026-07-31T20:05:14Z

Azure Pipelines: Successfully started running 4 pipeline(s). 12 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 · 2026-07-31T19:28:13Z

SuppressGCTransitionNegativeTest was failing under GC stress with Expected: -2146233082 / Actual: 100. PR #126108 replaced <GCStressIncompatible>true</GCStressIncompatible> with [SkipOnCoreClr(..., RuntimeTestModes.AnyGCStress)], but this test has a non-default CLRTestExitCode (crash exit code). An XUnit-level skip returns 100, which conflicts with the expected crash exit code the harness checks.

SuppressGCTransitionNegativeTest.csproj: Restore <GCStressIncompatible>true</GCStressIncompatible> so GC stress skipping happens at the wrapper-script level, not inside XUnit.
SuppressGCTransitionNegativeTest.cs: Remove the [SkipOnCoreClr] attribute that caused the XUnit-level skip.
requiresprocessisolation.md: Add Rule 30 — tests with a non-default CLRTestExitCode must use process-level skip mechanisms (e.g., GCStressIncompatible) rather than XUnit-level attributes; also add CLRTestExitCode to the summary table.

Note

This description was generated with AI assistance.

FixesFailed test: Interop/SuppressGCTransition/SuppressGCTransitionNegativeTest/SuppressGCTransitionNegativeTest #131667

Copilot

Copilot was unable to review this pull request because there is no eligible user to bill. To allow Copilot reviews on bot-authored pull requests, enable direct organization billing in your organization's Copilot settings.

azure-pipelines · 2026-07-31T19:28:32Z

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.

…d of SkipOnCoreClr The test sets CLRTestExitCode to a crash exit code, so an XUnit-level skip (which returns 100) conflicts with the expected exit code. Use the process-level GCStressIncompatible mechanism instead. Also document this requirement in requiresprocessisolation.md. Fixes#131667 Co-authored-by: jkoritzinsky <1571408+jkoritzinsky@users.noreply.github.com>

Copilot

Copilot was unable to review this pull request because there is no eligible user to bill. To allow Copilot reviews on bot-authored pull requests, enable direct organization billing in your organization's Copilot settings.

dotnet-policy-service · 2026-07-31T19:35:33Z

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

azure-pipelines · 2026-07-31T20:05:14Z

Azure Pipelines: Successfully started running 4 pipeline(s). 12 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 · 2026-07-31T19:28:13Z

SuppressGCTransitionNegativeTest was failing under GC stress with Expected: -2146233082 / Actual: 100. PR #126108 replaced <GCStressIncompatible>true</GCStressIncompatible> with [SkipOnCoreClr(..., RuntimeTestModes.AnyGCStress)], but this test has a non-default CLRTestExitCode (crash exit code). An XUnit-level skip returns 100, which conflicts with the expected crash exit code the harness checks.

SuppressGCTransitionNegativeTest.csproj: Restore <GCStressIncompatible>true</GCStressIncompatible> so GC stress skipping happens at the wrapper-script level, not inside XUnit.
SuppressGCTransitionNegativeTest.cs: Remove the [SkipOnCoreClr] attribute that caused the XUnit-level skip.
requiresprocessisolation.md: Add Rule 30 — tests with a non-default CLRTestExitCode must use process-level skip mechanisms (e.g., GCStressIncompatible) rather than XUnit-level attributes; also add CLRTestExitCode to the summary table.

Note

This description was generated with AI assistance.

FixesFailed test: Interop/SuppressGCTransition/SuppressGCTransitionNegativeTest/SuppressGCTransitionNegativeTest #131667

Copilot

Copilot was unable to review this pull request because there is no eligible user to bill. To allow Copilot reviews on bot-authored pull requests, enable direct organization billing in your organization's Copilot settings.

azure-pipelines · 2026-07-31T19:28:32Z

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.

…d of SkipOnCoreClr The test sets CLRTestExitCode to a crash exit code, so an XUnit-level skip (which returns 100) conflicts with the expected exit code. Use the process-level GCStressIncompatible mechanism instead. Also document this requirement in requiresprocessisolation.md. Fixes#131667 Co-authored-by: jkoritzinsky <1571408+jkoritzinsky@users.noreply.github.com>

Copilot

Copilot was unable to review this pull request because there is no eligible user to bill. To allow Copilot reviews on bot-authored pull requests, enable direct organization billing in your organization's Copilot settings.

dotnet-policy-service · 2026-07-31T19:35:33Z

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

azure-pipelines · 2026-07-31T20:05:14Z

Azure Pipelines: Successfully started running 4 pipeline(s). 12 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 · 2026-07-31T19:28:13Z

SuppressGCTransitionNegativeTest was failing under GC stress with Expected: -2146233082 / Actual: 100. PR #126108 replaced <GCStressIncompatible>true</GCStressIncompatible> with [SkipOnCoreClr(..., RuntimeTestModes.AnyGCStress)], but this test has a non-default CLRTestExitCode (crash exit code). An XUnit-level skip returns 100, which conflicts with the expected crash exit code the harness checks.

SuppressGCTransitionNegativeTest.csproj: Restore <GCStressIncompatible>true</GCStressIncompatible> so GC stress skipping happens at the wrapper-script level, not inside XUnit.
SuppressGCTransitionNegativeTest.cs: Remove the [SkipOnCoreClr] attribute that caused the XUnit-level skip.
requiresprocessisolation.md: Add Rule 30 — tests with a non-default CLRTestExitCode must use process-level skip mechanisms (e.g., GCStressIncompatible) rather than XUnit-level attributes; also add CLRTestExitCode to the summary table.

Note

This description was generated with AI assistance.

FixesFailed test: Interop/SuppressGCTransition/SuppressGCTransitionNegativeTest/SuppressGCTransitionNegativeTest #131667

Copilot

Copilot was unable to review this pull request because there is no eligible user to bill. To allow Copilot reviews on bot-authored pull requests, enable direct organization billing in your organization's Copilot settings.

azure-pipelines · 2026-07-31T19:28:32Z

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.

…d of SkipOnCoreClr The test sets CLRTestExitCode to a crash exit code, so an XUnit-level skip (which returns 100) conflicts with the expected exit code. Use the process-level GCStressIncompatible mechanism instead. Also document this requirement in requiresprocessisolation.md. Fixes#131667 Co-authored-by: jkoritzinsky <1571408+jkoritzinsky@users.noreply.github.com>

Copilot

Copilot was unable to review this pull request because there is no eligible user to bill. To allow Copilot reviews on bot-authored pull requests, enable direct organization billing in your organization's Copilot settings.

dotnet-policy-service · 2026-07-31T19:35:33Z

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

azure-pipelines · 2026-07-31T20:05:14Z

Azure Pipelines: Successfully started running 4 pipeline(s). 12 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 · 2026-07-31T19:28:13Z

SuppressGCTransitionNegativeTest was failing under GC stress with Expected: -2146233082 / Actual: 100. PR #126108 replaced <GCStressIncompatible>true</GCStressIncompatible> with [SkipOnCoreClr(..., RuntimeTestModes.AnyGCStress)], but this test has a non-default CLRTestExitCode (crash exit code). An XUnit-level skip returns 100, which conflicts with the expected crash exit code the harness checks.

SuppressGCTransitionNegativeTest.csproj: Restore <GCStressIncompatible>true</GCStressIncompatible> so GC stress skipping happens at the wrapper-script level, not inside XUnit.
SuppressGCTransitionNegativeTest.cs: Remove the [SkipOnCoreClr] attribute that caused the XUnit-level skip.
requiresprocessisolation.md: Add Rule 30 — tests with a non-default CLRTestExitCode must use process-level skip mechanisms (e.g., GCStressIncompatible) rather than XUnit-level attributes; also add CLRTestExitCode to the summary table.

Note

This description was generated with AI assistance.

FixesFailed test: Interop/SuppressGCTransition/SuppressGCTransitionNegativeTest/SuppressGCTransitionNegativeTest #131667

Copilot

Copilot was unable to review this pull request because there is no eligible user to bill. To allow Copilot reviews on bot-authored pull requests, enable direct organization billing in your organization's Copilot settings.

azure-pipelines · 2026-07-31T19:28:32Z

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.

…d of SkipOnCoreClr The test sets CLRTestExitCode to a crash exit code, so an XUnit-level skip (which returns 100) conflicts with the expected exit code. Use the process-level GCStressIncompatible mechanism instead. Also document this requirement in requiresprocessisolation.md. Fixes#131667 Co-authored-by: jkoritzinsky <1571408+jkoritzinsky@users.noreply.github.com>

Copilot

Copilot was unable to review this pull request because there is no eligible user to bill. To allow Copilot reviews on bot-authored pull requests, enable direct organization billing in your organization's Copilot settings.

dotnet-policy-service · 2026-07-31T19:35:33Z

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

azure-pipelines · 2026-07-31T20:05:14Z

Azure Pipelines: Successfully started running 4 pipeline(s). 12 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 · 2026-07-31T19:28:13Z

SuppressGCTransitionNegativeTest was failing under GC stress with Expected: -2146233082 / Actual: 100. PR #126108 replaced <GCStressIncompatible>true</GCStressIncompatible> with [SkipOnCoreClr(..., RuntimeTestModes.AnyGCStress)], but this test has a non-default CLRTestExitCode (crash exit code). An XUnit-level skip returns 100, which conflicts with the expected crash exit code the harness checks.

SuppressGCTransitionNegativeTest.csproj: Restore <GCStressIncompatible>true</GCStressIncompatible> so GC stress skipping happens at the wrapper-script level, not inside XUnit.
SuppressGCTransitionNegativeTest.cs: Remove the [SkipOnCoreClr] attribute that caused the XUnit-level skip.
requiresprocessisolation.md: Add Rule 30 — tests with a non-default CLRTestExitCode must use process-level skip mechanisms (e.g., GCStressIncompatible) rather than XUnit-level attributes; also add CLRTestExitCode to the summary table.

Note

This description was generated with AI assistance.

FixesFailed test: Interop/SuppressGCTransition/SuppressGCTransitionNegativeTest/SuppressGCTransitionNegativeTest #131667

Copilot

Copilot was unable to review this pull request because there is no eligible user to bill. To allow Copilot reviews on bot-authored pull requests, enable direct organization billing in your organization's Copilot settings.

azure-pipelines · 2026-07-31T19:28:32Z

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.

…d of SkipOnCoreClr The test sets CLRTestExitCode to a crash exit code, so an XUnit-level skip (which returns 100) conflicts with the expected exit code. Use the process-level GCStressIncompatible mechanism instead. Also document this requirement in requiresprocessisolation.md. Fixes#131667 Co-authored-by: jkoritzinsky <1571408+jkoritzinsky@users.noreply.github.com>

Copilot

Copilot was unable to review this pull request because there is no eligible user to bill. To allow Copilot reviews on bot-authored pull requests, enable direct organization billing in your organization's Copilot settings.

dotnet-policy-service · 2026-07-31T19:35:33Z

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

azure-pipelines · 2026-07-31T20:05:14Z

Azure Pipelines: Successfully started running 4 pipeline(s). 12 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 · 2026-07-31T19:28:13Z

SuppressGCTransitionNegativeTest was failing under GC stress with Expected: -2146233082 / Actual: 100. PR #126108 replaced <GCStressIncompatible>true</GCStressIncompatible> with [SkipOnCoreClr(..., RuntimeTestModes.AnyGCStress)], but this test has a non-default CLRTestExitCode (crash exit code). An XUnit-level skip returns 100, which conflicts with the expected crash exit code the harness checks.

SuppressGCTransitionNegativeTest.csproj: Restore <GCStressIncompatible>true</GCStressIncompatible> so GC stress skipping happens at the wrapper-script level, not inside XUnit.
SuppressGCTransitionNegativeTest.cs: Remove the [SkipOnCoreClr] attribute that caused the XUnit-level skip.
requiresprocessisolation.md: Add Rule 30 — tests with a non-default CLRTestExitCode must use process-level skip mechanisms (e.g., GCStressIncompatible) rather than XUnit-level attributes; also add CLRTestExitCode to the summary table.

Note

This description was generated with AI assistance.

FixesFailed test: Interop/SuppressGCTransition/SuppressGCTransitionNegativeTest/SuppressGCTransitionNegativeTest #131667

Copilot

Copilot was unable to review this pull request because there is no eligible user to bill. To allow Copilot reviews on bot-authored pull requests, enable direct organization billing in your organization's Copilot settings.

azure-pipelines · 2026-07-31T19:28:32Z

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.

…d of SkipOnCoreClr The test sets CLRTestExitCode to a crash exit code, so an XUnit-level skip (which returns 100) conflicts with the expected exit code. Use the process-level GCStressIncompatible mechanism instead. Also document this requirement in requiresprocessisolation.md. Fixes#131667 Co-authored-by: jkoritzinsky <1571408+jkoritzinsky@users.noreply.github.com>

Copilot

Copilot was unable to review this pull request because there is no eligible user to bill. To allow Copilot reviews on bot-authored pull requests, enable direct organization billing in your organization's Copilot settings.

dotnet-policy-service · 2026-07-31T19:35:33Z

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

azure-pipelines · 2026-07-31T20:05:14Z

Azure Pipelines: Successfully started running 4 pipeline(s). 12 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 · 2026-07-31T19:28:13Z

SuppressGCTransitionNegativeTest was failing under GC stress with Expected: -2146233082 / Actual: 100. PR #126108 replaced <GCStressIncompatible>true</GCStressIncompatible> with [SkipOnCoreClr(..., RuntimeTestModes.AnyGCStress)], but this test has a non-default CLRTestExitCode (crash exit code). An XUnit-level skip returns 100, which conflicts with the expected crash exit code the harness checks.

SuppressGCTransitionNegativeTest.csproj: Restore <GCStressIncompatible>true</GCStressIncompatible> so GC stress skipping happens at the wrapper-script level, not inside XUnit.
SuppressGCTransitionNegativeTest.cs: Remove the [SkipOnCoreClr] attribute that caused the XUnit-level skip.
requiresprocessisolation.md: Add Rule 30 — tests with a non-default CLRTestExitCode must use process-level skip mechanisms (e.g., GCStressIncompatible) rather than XUnit-level attributes; also add CLRTestExitCode to the summary table.

Note

This description was generated with AI assistance.

FixesFailed test: Interop/SuppressGCTransition/SuppressGCTransitionNegativeTest/SuppressGCTransitionNegativeTest #131667

Copilot

Copilot was unable to review this pull request because there is no eligible user to bill. To allow Copilot reviews on bot-authored pull requests, enable direct organization billing in your organization's Copilot settings.

azure-pipelines · 2026-07-31T19:28:32Z

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.

…d of SkipOnCoreClr The test sets CLRTestExitCode to a crash exit code, so an XUnit-level skip (which returns 100) conflicts with the expected exit code. Use the process-level GCStressIncompatible mechanism instead. Also document this requirement in requiresprocessisolation.md. Fixes#131667 Co-authored-by: jkoritzinsky <1571408+jkoritzinsky@users.noreply.github.com>

Copilot

Copilot was unable to review this pull request because there is no eligible user to bill. To allow Copilot reviews on bot-authored pull requests, enable direct organization billing in your organization's Copilot settings.

dotnet-policy-service · 2026-07-31T19:35:33Z

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

azure-pipelines · 2026-07-31T20:05:14Z

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

Initial plan
c8c8b42

CopilotAI assigned Copilot and jkoritzinsky Jul 31, 2026

CopilotAI review requested due to automatic review settings July 31, 2026 19:28

github-project-automationBot added this to AppModel Jul 31, 2026

CopilotAI reviewed Jul 31, 2026
View reviewed changes

CopilotAI linked an issue Jul 31, 2026 that may be closed by this pull request
Failed test: Interop/SuppressGCTransition/SuppressGCTransitionNegativeTest/SuppressGCTransitionNegativeTest #131667
Closed

Copilotstarted work on behalf of jkoritzinsky July 31, 2026 19:29 View session

github-actionsBot added the area-GC-coreclr label Jul 31, 2026

CopilotAI review requested due to automatic review settings July 31, 2026 19:35

CopilotAI reviewed Jul 31, 2026
View reviewed changes

CopilotAI changed the title ~~[WIP] Fix failed test for SuppressGCTransitionNegativeTest~~Fix SuppressGCTransitionNegativeTest: restore GCStressIncompatible, document CLRTestExitCode requirementJul 31, 2026

CopilotAI requested a review from jkoritzinsky July 31, 2026 19:40

Copilotfinished work on behalf of jkoritzinsky July 31, 2026 19:40

jkoritzinsky approved these changes Jul 31, 2026
View reviewed changes

jkoritzinsky marked this pull request as ready for review July 31, 2026 20:04

jkotas approved these changes Jul 31, 2026
View reviewed changes

jkoritzinsky enabled auto-merge (squash) July 31, 2026 21:35

jkoritzinsky merged commit 2de3951 into mainJul 31, 2026
84 checks passed

jkoritzinsky deleted the copilot/fix-suppress-gc-transition-test branch July 31, 2026 22:22

github-project-automationBot moved this to Done in AppModel Jul 31, 2026

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

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

EgorBo mentioned this pull request Aug 3, 2026
Migrate JitOptimizationSensitive and GCStressIncompatible to SkipOnCoreClr attributes #126108
Merged

github-actionsBot locked and limited conversation to collaborators Sep 2, 2026