Fix JitBench (#19584)
authorKoundinya Veluri <kouvel@users.noreply.github.com>
Fri, 24 Aug 2018 19:33:56 +0000 (12:33 -0700)
committerGitHub <noreply@github.com>
Fri, 24 Aug 2018 19:33:56 +0000 (12:33 -0700)
commit98c34c45f9ad3ec93bf4192735621341506f0550
tree2a3ee9a6258761980fc4aff30a03ac2a472a6369
parent54898e0e26dac2f15563b7615f9139ef532b5fc5
Fix JitBench (#19584)

Fix JitBench

Fixes https://github.com/dotnet/coreclr/issues/19569
- I believe the issue was that JitBench (which was an netstandard1.6 project) was running against a netcoreapp3.0 layout with corerun (layout built by build + recent packages), and XmlDocument is in a different place now
- Copied the unofficial project and replaced the official one
- Switched to netcoreapp3.0 along with other miscellaneous fixes to get it working
- I haven't figured out yet how to get one project that builds with the test build and works with dotnet. TargetFramework would have to be different anyway if running with dotnet runtime 2.1. So the unofficial project is still there for use with dotnet.
- Also retargeted the empty console project and changed to always set ExePath (when using existing setup for instance)
tests/src/performance/Scenario/JitBench/Benchmarks/EmptyConsoleProgramExecution.cs
tests/src/performance/Scenario/JitBench/JitBench.csproj
tests/src/performance/Scenario/JitBench/Runner/Benchmark.cs
tests/src/performance/Scenario/JitBench/unofficial_dotnet/Directory.Build.props [moved from tests/src/performance/Scenario/JitBench/Directory.Build.props with 100% similarity]
tests/src/performance/Scenario/JitBench/unofficial_dotnet/Directory.Build.targets [moved from tests/src/performance/Scenario/JitBench/Directory.Build.targets with 100% similarity]