Revert "[mono][interp] Improve tiering performance (dotnet#70649)" #73187
Conversation
|
/azp run runtime-wasm |
|
Tagging subscribers to this area: @BrzVlad Issue Detailsin AOT we may not have fields inited if we're using cached class info. Fixes #73180
|
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Nope, that wasn't enough. still failing https://helix.dot.net/api/2019-06-17/jobs/75f26afc-7835-4238-9f6c-1006f01fba71/workitems/normal-System.Xml.XmlSerializer.Tests/console |
|
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Adding initializations, and asserting that the class isn't marked with a failure didn't help. I guess the stack trace could be misleading. Need to try and repro locally. |
|
Trying to revert #70649 to see if that resolves it |
|
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
This reverts commit 01444f7.
lambdageek
force-pushed
the
try-fix-gh-73180
branch
from
c8618ae to
13513b5
Compare
|
Reverting #70649 fixes the crash |
lambdageek
changed the title
|
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Closing in favor of #73264 |
ghost
locked as resolved and limited conversation to collaborators
2 participants
in AOT we may not have fields inited if we're using cached class info.
Fixes #73180