-
Notifications
You must be signed in to change notification settings - Fork 268
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
Enable wasm aot microbenchmark run #1902
Merged
Merged
Changes from all commits
Commits
Show all changes
49 commits
Select commit
Hold shift + click to select a range
ff341e4
copy back the helix job folder for diagnosis
Lxiamail a1b4109
copy back the helix job folder for diagnosis
Lxiamail a4e9600
Merge branch 'alicial/hikeMicro-benchmark' of https://github.com/dotn…
Lxiamail ef302af
hack:setting WasmNativeWorkload=false for wasm run. should be removed…
Lxiamail d0709a5
fixed merge confict
Lxiamail 62b5514
fix copyjob
Lxiamail b7c61b1
move copy helix job-* folder code to benchmarks_ci.py
Lxiamail fc72b62
update benchmarkdotnet version
Lxiamail 9ebeee7
add more log info for diagnosis
Lxiamail da5b930
suppress an unnecessory exception
Lxiamail 35e3c41
fix copy back job-* folder
Lxiamail e386e4e
fix copy job
Lxiamail 4e0e027
correct helixuploadroot
Lxiamail d6abd59
add error handling
Lxiamail 023ef60
fix copy path
Lxiamail 6035f55
enabled binlog
Lxiamail ac4dcdc
rethrow
Lxiamail ab97a6b
add back copy job folder for diagnosis
Lxiamail 0049153
dotnet workload install wasm-tools to work around missing workload error
Lxiamail 8448dc7
run dotnet workload install wasm-tools from dotnet-wasm directory to …
Lxiamail b890b88
install wasm-tools workload from perf directory
Lxiamail 29ab2eb
install wasm-tools workload with a specific nuget.config with wasm feed
Lxiamail ebbfe38
fix path
Lxiamail 2f8b61e
workdir of install wasm-tools
Lxiamail fe45b23
Get PR#1891 from main
Lxiamail a35a0c7
update to new version of benchmarkdotnet for wasm aot fixes
Lxiamail 8815bc5
add -d to print diagnostic info for wasm_tools workload installation …
Lxiamail a537566
Allow to build with local BenchmarkDotNet sources
radekdoulik 1d11a28
Set _BenchmarkDotNetSourcesN conditionaly
radekdoulik ea28179
Use _BenchmarkDotNetSourcesN
radekdoulik 4a4ca92
Use BenchmarkDotNet sources in payload
radekdoulik d566d6b
update to newer benchmarkdotnet version
Lxiamail a69d693
remove testing code
Lxiamail 3ffe4d7
update bdn version
Lxiamail 0132916
Merge branch 'main' into alicial/wasmaotmicro
Lxiamail 7c5b5a1
remove duplicated section
Lxiamail badd062
print out args.configuration for diagnosis
Lxiamail 6c383ce
print args
Lxiamail a6f66d3
print args
Lxiamail 1025c15
minor fix
Lxiamail 2056b08
looks up wasm in ExtraBenchmarkDotNetArguments
Lxiamail aee0c2e
check wasmEngine for wasm runs
Lxiamail c49c485
minor fix
Lxiamail 272a41f
minor fix
Lxiamail 4b2930b
remove work around code for install wasm_tools workload, WasmNativeWo…
Lxiamail 72924ae
add back Directory.Build.props to see if can work around an aot build…
Lxiamail 8b2dc7d
Merge branch 'main' into alicial/wasmaotmicro
Lxiamail 56027a4
disable FlushAsync test from wasm run since async is not supported.
Lxiamail 81bad40
Merge branch 'alicial/wasmaotmicro' of https://github.com/dotnet/perf…
Lxiamail File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
<?xml version="1.0" encoding="utf-8"?> | ||
<Project> | ||
<PropertyGroup> | ||
<WasmNativeWorkload>false</WasmNativeWorkload> | ||
</PropertyGroup> | ||
</Project> | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
<?xml version="1.0" encoding="utf-8"?> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This nuget,config is used when installs emsdk in performance-setup.sh file |
||
<configuration> | ||
<packageSources> | ||
<clear /> | ||
<add key="dotnet-public" value="https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-public/nuget/v3/index.json" /> | ||
<add key="dotnet6" value="https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet6/nuget/v3/index.json" /> | ||
<add key="nuget.org" value="https://api.nuget.org/v3/index.json" protocolVersion="3" /> | ||
<add key="xamarin" value="https://pkgs.dev.azure.com/azure-public/vside/_packaging/xamarin-impl/nuget/v3/index.json" /> | ||
<add key="dotnet-eng" value="https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-eng/nuget/v3/index.json" /> | ||
<add key="dotnet-tools" value="https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-tools/nuget/v3/index.json" /> | ||
<add key="benchmark-dotnet-prerelease" value="https://pkgs.dev.azure.com/dnceng/public/_packaging/benchmark-dotnet-prerelease/nuget/v3/index.json" /> | ||
</packageSources> | ||
</configuration> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Why do we need this file in the
docs
folder?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.
Good question. :) The goal is put this Directory.Build.props file to a root/parent directory where benchmarkdotnet runs from. Due to we copy docs directory to workitemdirectory, having Directory.Build.props file in the same directory makes it work. However, we should remove ASAP since this could have unexpected back consequences. opened #1909 to track this.