-
Notifications
You must be signed in to change notification settings - Fork 5.2k
[wasm] Fix performance-setup.sh to track change in BDN #92067
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
Conversation
`dotnet/performance` got an update for `dotnet/BenchmarkDotNet` via dotnet/performance#3331 . And that bdn update includes dotnet/BenchmarkDotNet#2375, which subtly changes how the arguments get parsed, and breaks the existing scripts: ``` $ pushd "/home/helixbot/work/B807097D/w/AED609DF/e/performance/artifacts/bin/for-running/MicroBenchmarks" $ dotnet exec MicroBenchmarks.dll --wasmArgs "--experimental-wasm-eh --expose_wasm --module" ... MicroBenchmarks 1.0.0-dev © Microsoft Corporation. All rights reserved. ERROR(S): Option 'experimental-wasm-eh --expose_wasm --module' is unknown. ``` Fixes dotnet#92066 .
|
Tagging subscribers to 'arch-wasm': @lewing Issue Details
Fixes #92066 .
|
|
Test run - https://dev.azure.com/dnceng/internal/_build/results?buildId=2267326 . I will stop that once any one of the microbenchmarks run successfully. |
|
Tagging subscribers to this area: @directhex Issue Details
Fixes #92066 .
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks for the fix!
|
Successful test run in https://dev.azure.com/dnceng/internal/_build/results?buildId=2267699 . |
|
Merging to unblock the pipeline, and the CI checks here won't be testing the changes anyway. |
dotnet/performancegot an update fordotnet/BenchmarkDotNetviadotnet/performance#3331 . And that bdn update
includes dotnet/BenchmarkDotNet#2375, which
subtly changes how the arguments get parsed, and breaks the existing
scripts:
Fixes #92066 .