You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Runtime_133101.Runtime_133101.TestEntryPoint consistently crashes the Regression_ro_2 merged test process when run by Windows x64 Mono MiniJIT. The failure occurs across unrelated pull-request builds and different Helix machines.
Reproduction Steps
Run JIT/Regression/Regression_ro_2 in the windows-x64 Release AllSubsets_Mono_Minijit_RuntimeTests minijit leg.
The test passes and the merged test process exits with code 100.
Actual behavior
corerun terminates with Windows access violation 0xC0000005 (-1073741819) immediately after starting Runtime_133101.Runtime_133101.TestEntryPoint.
Regression?
The test was recently added to Regression_ro_2; the same crash has since appeared in numerous unrelated runtime PR builds.
Known Workarounds
Exclude Runtime_133101 from the merged test project for Windows x64 Mono MiniJIT while keeping it enabled for other configurations.
Configuration
Runtime: Mono MiniJIT
OS: Windows 11
Architecture: x64
Test work item: Regression_ro_2
Other information
The failure does not produce a TRX result for the crashing test, so Build Analysis cannot validate a sufficiently specific Known Build Error signature. The issue is therefore used as an ActiveIssue tracker for a configuration-specific test exclusion.
Note
This issue was generated with GitHub Copilot.
Known Issue Error Message
DO NOT USE JSON BELOW IF THIS IS A BUILD BREAK otherwise build analysis will allow pull requests to merge that break the build worse. For a build break, do not use this issue form. Make a regular new issue.
Description
Runtime_133101.Runtime_133101.TestEntryPointconsistently crashes theRegression_ro_2merged test process when run by Windows x64 Mono MiniJIT. The failure occurs across unrelated pull-request builds and different Helix machines.Reproduction Steps
Run
JIT/Regression/Regression_ro_2in thewindows-x64 Release AllSubsets_Mono_Minijit_RuntimeTests minijitleg.The final test output is:
Example build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1586954
Example console log: https://helixr18s23ayyejvk1x8qcc.blob.core.windows.net/dotnet-runtime-refs-pull-133367-merge-d06948e5e63e4cfe8e/Regression_ro_2/1/console.ce0c2d1f.log?helixlogtype=result
Expected behavior
The test passes and the merged test process exits with code 100.
Actual behavior
corerunterminates with Windows access violation0xC0000005(-1073741819) immediately after startingRuntime_133101.Runtime_133101.TestEntryPoint.Regression?
The test was recently added to
Regression_ro_2; the same crash has since appeared in numerous unrelated runtime PR builds.Known Workarounds
Exclude
Runtime_133101from the merged test project for Windows x64 Mono MiniJIT while keeping it enabled for other configurations.Configuration
Regression_ro_2Other information
The failure does not produce a TRX result for the crashing test, so Build Analysis cannot validate a sufficiently specific Known Build Error signature. The issue is therefore used as an ActiveIssue tracker for a configuration-specific test exclusion.
Note
This issue was generated with GitHub Copilot.
Known Issue Error Message
DO NOT USE JSON BELOW IF THIS IS A BUILD BREAK otherwise build analysis will allow pull requests to merge that break the build worse. For a build break, do not use this issue form. Make a regular new issue.
Fill the error message using step by step known issues guidance.
{ "ErrorMessage": "", "ErrorPattern": "", "BuildRetry": false, "ExcludeConsoleLog": false }Report
Summary