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

[wasm] Set the right runtime moniker #1932

Merged
merged 2 commits into from
Mar 3, 2022

Conversation

radekdoulik
Copy link
Member

@radekdoulik radekdoulik commented Mar 2, 2022

Fix dotnet/performance#2250

Commit 80f45ce started using the runtime moniker to decide, which
main JS file to use. We use test-main.js in net7.0, while we were
using main.js in older versions.

To make that work, let set the right runtime moniker to WasmRuntime. So
that later in Executor::ProcessStartInfo we select the right file.

Fix dotnet/performance#2250

Commit 80f45ce started using the runtime moniker to decide, which
main JS file to use. We use `test-main.js` in net7.0, while we were
using `main.js` in older versions.

To make that work, let set the right runtime moniker to WasmRuntime. So
that later in `Executor::ProcessStartInfo` we select the right file.
@lewing
Copy link
Member

lewing commented Mar 2, 2022

cc @adamsitnik @naricc

Copy link
Member

@adamsitnik adamsitnik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thank you @radekdoulik !

src/BenchmarkDotNet/ConsoleArguments/ConfigParser.cs Outdated Show resolved Hide resolved
src/BenchmarkDotNet/ConsoleArguments/ConfigParser.cs Outdated Show resolved Hide resolved
default:
return false;
}
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in the future we might want to move it to RuntimeMonikerExtensions

@naricc
Copy link

naricc commented Mar 2, 2022

Looks good to me.

@radekdoulik
Copy link
Member Author

The build / build-windows fails with:

Standard error: 
  C:\Users\runneradmin\.nuget\packages\microsoft.dotnet.ilcompiler\6.0.0-rc.1.21420.1\build\Microsoft.NETCore.Native.Windows.props(109,5): error : Platform linker not found. To fix this problem, download and install Visual Studio 2019 from http://visualstudio.com./ Make sure to install the Desktop Development for C++ workload. For ARM64 development also install C++ ARM64 build tools. [D:\a\BenchmarkDotNet\BenchmarkDotNet\tests\BenchmarkDotNet.IntegrationTests\bin\Release\net5.0\ddeb76ef-2c31-458a-be4f-b5769587df56\BenchmarkDotNet.Autogenerated.csproj]

Is that new fail? From quick look it seems unrelated.

@radekdoulik
Copy link
Member Author

Actually I see it fail elsewhere too, so it is not related to this change.

@adamsitnik adamsitnik merged commit ca51035 into dotnet:master Mar 3, 2022
@AndreyAkinshin AndreyAkinshin added this to the v0.13.2 milestone Apr 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

WASM Microbenchmarks Not Working
5 participants