R2R jobs are failing with Fatal error. Internal CLR error. (0x80131506) #43198
Labels
area-Infrastructure-coreclr
blocking-outerloop
Blocking the 'runtime-coreclr outerloop' and 'runtime-libraries-coreclr outerloop' runs
test-run-core
Test failures in .NET Core test runs
Milestone
Comments
sandreenko
added
test-run-core
Dotnet-GitSync-Bot
added
the
untriaged
|
#13590 seems unrelated; the user claims it only reproduces with a debugger attached. Taking a look to see if anything stands out. |
|
The diff for good -> bad is:
From the one you sent, looking at one of the dumps: Stack of crash from baseservices.callconvs (AV)Instantiation MethodTable::GetInstantiation()
{
LIMITED_METHOD_CONTRACT;
SUPPORTS_DAC;
if (HasInstantiation())
{
PTR_GenericsDictInfo pDictInfo = GetGenericsDictInfo();
-> TADDR base = dac_cast<TADDR>(&(GetPerInstInfo()[pDictInfo->m_wNumDicts-1]));
return Instantiation(PerInstInfoElem_t::GetValueMaybeNullAtPtr(base)->GetInstantiation(), pDictInfo->m_wNumTyPars);
}
else
{
return Instantiation();
}
}Method Table & generic: So |
jeffschwMSFT
removed
the
untriaged
|
I think this was definitely in some way affected by JanV's change to switch over framework compilation to use the r2rtest tool, the only trouble is that so far I've been unable to nail down the exact problem. I haven't yet managed to repro this locally even though it's most likely that some subtle bug in framework compilation is to blame. I have a PR out where I fixed the remaining inconsistencies w.r.t. the r2rtest framework compilation change, and a bit of a good news is that with the change all Crossgen2 legs seem to fail in a relatively consistent manner - crashing upon launch of the XUnit wrappers. I continue investigating this, an interesting tell-tale sign in some runs is a failure to "validate the layout of System.Object", I'm currently following up on this one in the hope that it will shed more light on the inconsistency. |
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
All recent outer loop runs are red because of all R2R jobs are failing.
The tests are failing with:
#13590 could be related
I think it started with https://dev.azure.com/dnceng/public/_build/results?buildId=838111&view=ms.vss-test-web.build-test-results-tab but there are 250 changes in this chunk so can't find suspicion changes.
PTAL @hoyosjs @dotnet/runtime-infrastructure , cc @dotnet/jit-contrib
The text was updated successfully, but these errors were encountered: