Enable jit optimization in crossgen testing#114464
Conversation
Also mark `filter` test entry point as `aggressiveinlining` to create a cross-assembly wrapped exception throw test when crossgen2 runs in composite mode. (see dotnet#113815 / dotnet#113849)
|
Seems like we should generally run crossgen2 tests with jit optimizations enabled. @steveisok @jkotas PTAL |
|
/azp run runtime-coreclr crossgen2 outerloop |
|
Azure Pipelines successfully started running 1 pipeline(s). |
This makes the test fail due to the bug that you are fixing. |
jkotas
left a comment
There was a problem hiding this comment.
LGTM if the change does not introduce any new test failures.
|
Windows script change has There are a bunch of failures of the form Also this test is probably optimization sensitive |
|
/azp run runtime-coreclr crossgen2 outerloop |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Yes, want to make sure it actually fails. Looks like it does: |
|
It looks like So we can't yet enable optimization. |
|
Going to try just enabling for windows, opened #114504 for the Linux R2R composite issue. |
|
/azp run runtime-coreclr crossgen2 outerloop |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
None of the failures seems related: Crossgen2 OSX failure is #109395 Wasm failure looks like low-memory / oom x86 failure is in tracing/eventpipe/diagnosticport/diagnosticport/diagnosticport.cmd |
Also mark
filtertest entry point asaggressiveinliningto create a cross-assembly wrapped exception throw test when crossgen2 runs in composite mode.(see #113815 / #113849)