Skip to content

Disable CoreCLR interpreter test for JIT stress #116219

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

janvorli
Copy link
Member

@janvorli janvorli commented Jun 2, 2025

There is a problem in the interpreter when handling calls to code that doesn't have native code yet, but that has precode already. The call to MethodDesc::PrepareInitialCode triggers an assert down its call chain due to the prestub existence.

This change disables running the interpreter test with JIT stress until the problem is solved.

There is a problem in the interpreter when handling calls to code that
doesn't have native code yet, but that has precode already. The call to
MethodDesc::PrepareInitialCode triggers an assert down its call chain
due to the prestub existence.

This change disables running the interpreter test with JIT stress until
the problem is solved.
@janvorli janvorli added this to the 10.0.0 milestone Jun 2, 2025
@janvorli janvorli requested a review from jakobbotsch June 2, 2025 15:44
@janvorli janvorli self-assigned this Jun 2, 2025
@Copilot Copilot AI review requested due to automatic review settings June 2, 2025 15:44
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR disables the CoreCLR interpreter test for JIT stress due to an issue with generating interpreter bytecode for methods that already have a prestub.

  • Updated the InterpreterTester.csproj file to include a new property that disables the test under JIT stress.
  • Added a comment explaining the temporary disablement and linking to the corresponding runtime issue.
Comments suppressed due to low confidence (1)

src/tests/JIT/interpreter/InterpreterTester.csproj:11

  • [nitpick] The property name 'JitOptimizationSensitive' might be ambiguous as it does not clearly indicate that the interpreter test is being disabled under JIT stress. Consider renaming it to something like 'DisableInterpreterTestUnderJitStress' for improved clarity.
<JitOptimizationSensitive>true</JitOptimizationSensitive>

Copy link
Contributor

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

@janvorli janvorli merged commit 39e8c08 into dotnet:main Jun 2, 2025
74 checks passed
@janvorli janvorli deleted the disable-interpreter-test-with-jit-stress branch June 2, 2025 18:21
@github-actions github-actions bot locked and limited conversation to collaborators Jul 3, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants