-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
R2R tests failing: Fatal error. Internal CLR error. (0x80131506) #44807
Comments
These all started failing on 11/12 evening's scheduled runs. Could be related to #38457 since that was the only interesting infra change that day. I'll see if it repros locally. |
I was not able to repro it directly, the first failing run included these changes https://dev.azure.com/dnceng/public/_traceability/runview/changes?currentRunId=885251 |
According to the AzDO pipeline log we're still using dotnet v5 as the CLI to run apps in Helix. I'm wondering whether it can be now causing problems if the tests claim to be targeting .NET 6. I'm also unable to repro locally and this is exactly the type of problem one can only see in Helix. I'll try to put up an instrumented run changing this to 6. F:\workspace\_work\1\s\.dotnet\sdk\5.0.100-rc.2.20479.15\MSBuild.dll /nologo -maxcpucount /m /maxcpucount -verbosity:m /v:minimal /bl:F:\workspace\_work\1\s/artifacts/log/SendToHelix.binlog /clp:Summary /logger:F:\workspace\_work\1\s\.packages\microsoft.dotnet.arcade.sdk\6.0.0-beta.20552.5\tools\netcoreapp2.1\Microsoft.DotNet.Arcade.Sdk.dll /nr:False /p:ContinuousIntegrationBuild=True /p:TreatWarningsAsErrors=true /p:TargetArchitecture=x64 /p:TargetOS=windows /p:TargetOSSubgroup= /p:Configuration=Checked /warnaserror F:\workspace\_work\1\s/src/tests/Common/helixpublishwitharcade.proj DotNetCliVersion: 5.0.0 DotNetCliPackageType: runtime |
My PR didn't change anything in the CoreCLR build or test infra outside of some signing changes in the official build. The failure seems to be happening in the CLI we pull down for testing, which is .NET 5.0 release as far as I can tell. The crash is at https://github.com/dotnet/runtime/blob/release/5.0/src/coreclr/src/vm/methodtable.cpp#L5907 |
David noticed we have multiple copies of some framework assemblies loaded in the crash dump. Running |
The R2R tests are passing now in recent runtime outerloop runs. |
Thanks Simon for fixing this so quickly! |
It appears that all R2R tests are failing, as follows:
This is for the R2R legs in the
runtime-coreclr outerloop
job, as well as the R2R specific jobs,runtime-coreclr r2r
andruntime-coreclr r2r-extra
. The crossgen2 and crossgen2-composite jobs are failing the same way.https://dev.azure.com/dnceng/public/_build/results?buildId=888886&view=results
https://dev.azure.com/dnceng/public/_build/results?buildId=888602&view=results
https://dev.azure.com/dnceng/public/_build/results?buildId=887202&view=results
https://dev.azure.com/dnceng/public/_build/results?buildId=887278&view=results
https://dev.azure.com/dnceng/public/_build/results?buildId=887276&view=results
@dotnet/crossgen-contrib @mangod9
The text was updated successfully, but these errors were encountered: