-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Test failure: ValueFactory attempted to access the Value property of this instance. #100476
Comments
Failed in: runtime-coreclr jitstress2-jitstressregs 20240406.1 Failed tests:
Error message:
Stack trace:
|
@janvorli - This test passes with |
Failed in: runtime-coreclr jitstress2-jitstressregs 20240414.1 Failed tests:
Error message:
Stack trace:
|
@kunalspathak I am unable to repro it on my Apple M1. I've set COMPlus_TieredCompilation=0 COMPlus_JitStress=2 COMPlus_JitStressRegs=0x80 and ran the |
Actually, the merged tests don't return any error code from the test run, so I've missed that the test is failing. But for me, it is failing quite differently:
|
Interestingly, without COMPlus_JitStress=2, it doesn't call the |
and what happens when you set |
Failed in: runtime-coreclr jitstress2-jitstressregs 20240421.1 Failed tests:
Error message:
Stack trace:
|
Exactly the same as without it. |
It is still failing in runtime-coreclr jitstress2-jitstressregs. |
I pulled in the latest artifacts from https://dev.azure.com/dnceng-public/public/_build/results?buildId=664183&view=ms.vss-test-web.build-test-results-tab&runId=16472434&resultId=105819&paneView=debug and was able to repro it on my Mac M2: ![]() |
I can repro it with runfo using the build from your recent link. |
When I've made a change to optimize the collided exception handling by copying the stack frame iterator state, I've somehow missed adding two callee saved registers, x27 and x28 to a list of callee saved registers and that caused them to not to be copied during the state copying. It has caused failures in one of the coreclr tests when running with specific JIT stress settings. Close dotnet#100476
When I've made a change to optimize the collided exception handling by copying the stack frame iterator state, I've somehow missed adding two callee saved registers, x27 and x28 to a list of callee saved registers and that caused them to not to be copied during the state copying. It has caused failures in one of the coreclr tests when running with specific JIT stress settings. Close #100476
When I've made a change to optimize the collided exception handling by copying the stack frame iterator state, I've somehow missed adding two callee saved registers, x27 and x28 to a list of callee saved registers and that caused them to not to be copied during the state copying. It has caused failures in one of the coreclr tests when running with specific JIT stress settings. Close dotnet#100476
When I've made a change to optimize the collided exception handling by copying the stack frame iterator state, I've somehow missed adding two callee saved registers, x27 and x28 to a list of callee saved registers and that caused them to not to be copied during the state copying. It has caused failures in one of the coreclr tests when running with specific JIT stress settings. Close dotnet#100476
Failed in: runtime-coreclr jitstress2-jitstressregs 20240331.1
Failed tests:
Error message:
Stack trace:
The text was updated successfully, but these errors were encountered: