Skip to content

Remove the dead clrinterpreter runtime-test scenario - #134805

Merged
lewing merged 1 commit into
mainfrom
lewing-remove-dead-clrinterpreter-scenario
Sep 29, 2026
Merged

lewing merged 1 commit into
mainfrom
lewing-remove-dead-clrinterpreter-scenario

Conversation

@lewing

@lewing lewing commented Sep 28, 2026

Copy link
Copy Markdown
Member

Removes the clrinterpreter scenario from src/tests/Common/testenvironment.proj: the TestEnvironment entry and the _TestEnvFileLine items (both the Windows set and Unix export variants) that were conditioned on it.

The scenario is dead:

  • It sets DOTNET_Interpret, DOTNET_InterpreterHWIntrinsicsIsSupportedFalse, DOTNET_InterpreterJITThreshold, and DOTNET_InterpreterDoLoopMethods. None of these exist as runtime config values today; clrconfigvalues.h only defines Interpreter, InterpMode, InterpreterName, and InterpreterPath. They came from the legacy CoreCLR interpreter, which was removed long ago. The only later change to these lines was the mechanical COMPlus_ → DOTNET_ rename (Use DOTNET_ variables in tests #76997).
  • No pipeline uses the scenario. The current CoreCLR interpreter lanes use interpmode1–interpmode3, which set DOTNET_InterpMode. The -clrinterpreter build flag used in runtime-diagnostics.yml is a separate thing and this PR doesn't change it.

Validation: ran CreateTestEnvFile for interpmode1 and jitstress1 with both Windows and osx targets, before and after the change. The generated env files are byte-identical.

Note

This PR description was generated with GitHub Copilot.

The clrinterpreter scenario set DOTNET_Interpret, DOTNET_InterpreterJITThreshold,
DOTNET_InterpreterHWIntrinsicsIsSupportedFalse and DOTNET_InterpreterDoLoopMethods,
which belonged to the long-removed legacy CoreCLR interpreter and no longer exist.
No pipeline uses the scenario; the current interpreter lanes use interpmode1-3.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@azure-pipelines

Copy link
Copy Markdown
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.

@dotnet-policy-service

Copy link
Copy Markdown
Contributor

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

@lewing
lewing requested a review from jkotas September 28, 2026 18:05
@jkotas

jkotas commented Sep 28, 2026

Copy link
Copy Markdown
Member

For reference, originally introduce by #38650

@lewing
lewing enabled auto-merge (squash) September 28, 2026 21:01
@lewing

lewing commented Sep 29, 2026

Copy link
Copy Markdown
Member Author

/ba-g slow Mac is stuck

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants