Skip to content
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

Run runtime tests marked as JitOptimizationSensitive on Mono. #58106

Conversation

lateralusX
Copy link
Member

Several EventPipe tests marked as JitOptimizationSensitive and are currently skipped on Mono CI. PR enables no_tiered_compilation when running CI test runs on Mono to make sure these tests gets executed as well.

@ghost
Copy link

ghost commented Aug 25, 2021

Tagging subscribers to this area: @directhex
See info in area-owners.md if you want to be subscribed.

Issue Details

Several EventPipe tests marked as JitOptimizationSensitive and are currently skipped on Mono CI. PR enables no_tiered_compilation when running CI test runs on Mono to make sure these tests gets executed as well.

Author: lateralusX
Assignees: -
Labels:

area-Infrastructure-mono

Milestone: -

@lateralusX
Copy link
Member Author

Seems to do the trick, EventPipe tests running including a new JIT test that also fails. Fix for at least one failed EventPipe tests is already included in #58099, so once that gets merge this PR can be rerun. Need to investigate why new JIT tests previously not run on Mono fails and if we should disable it as part of this PR.

@lateralusX lateralusX force-pushed the lateralusX/enable-jit-sensetive-test-on-mono branch from 30d644e to 04f16ba Compare August 26, 2021 12:01
@lateralusX
Copy link
Member Author

Down to test failures on llvmaot config but tests now runs and pass on OSX (x64), Linux (arm64) using JIT and on Linux (arm64) and OSX(x64) using interpreter. Have run diagnostic tracing and runtime counters on iOS llvmaot without issues, so failures in:

runtime (Mono llvmaot Pri0 Runtime Tests Run Linux arm64 release)
runtime (Mono llvmaot Pri0 Runtime Tests Run Linux x64 release)

Could be related to build or ILLinker settings used on CI. Needs further investigation, but short term I believe its is good to get the working platforms up and running and exclude failing tests on above CI lanes and add issue to fix it in net7 timeframe.

Have never run on Mono in the past and was enabled when enabling
running JIT sensetive tests.
Building Cross Compiler will rebuild S.P.C and patching CORE_ROOT
after will replace with S.P.C from Cross Compiler build instead
of using the one from donwloaded product build.
@lateralusX lateralusX force-pushed the lateralusX/enable-jit-sensetive-test-on-mono branch from bf67129 to 15f2465 Compare August 31, 2021 06:40
@lateralusX
Copy link
Member Author

Introducing error in EventPipe to make sure we see test failures on CI.

@lateralusX
Copy link
Member Author

Observed expected failures in EventPipe tests, proving that tests are running as part of CI with changes in this PR.

@lateralusX lateralusX force-pushed the lateralusX/enable-jit-sensetive-test-on-mono branch from a48bba3 to 15f2465 Compare August 31, 2021 13:15
@lateralusX
Copy link
Member Author

Reverted EventPipe error used to test CI failures in EventPipe tests.

@lateralusX lateralusX changed the title WIP: Run runtime tests marked as JitOptimizationSensitive on Mono. Run runtime tests marked as JitOptimizationSensitive on Mono. Aug 31, 2021
@lateralusX lateralusX marked this pull request as ready for review August 31, 2021 13:16
@lateralusX
Copy link
Member Author

lateralusX commented Aug 31, 2021

@SamMonoRT, FYI, PR makes sure we run runtime tests marked as JIT sensitive on CI. Couple of EventPipe tests was not run on platforms we expected them to run, not capturing a regression in Mono when fixing a EventPipe failure in CoreCLR.

@lateralusX lateralusX merged commit 49ea27e into dotnet:main Sep 2, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Oct 2, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants