-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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] Move microbenchmarks, and blazor SOD runs to net8.0 #80308
Conversation
Tagging subscribers to 'arch-wasm': @lewing Issue Detailsnull
|
/azp run runtime-wasm-perf |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm-perf |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm-perf |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm-perf |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm-perf |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm-perf |
Azure Pipelines failed to run 1 pipeline(s). |
/azp run runtime-wasm-perf |
Azure Pipelines failed to run 1 pipeline(s). |
/azp run runtime-wasm-perf |
Azure Pipelines failed to run 1 pipeline(s). |
/azp run runtime-wasm-perf |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm-perf |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm-perf |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm-perf |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm-perf |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm-perf |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm-perf |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm-perf |
Azure Pipelines successfully started running 1 pipeline(s). |
- this is because jsvu fails to generate a wrapper for the specific version, because this version of jsvu (2.0.1) is broken with node 14.x . And node 18.x builds are not built for ubuntu 18.04
Also waiting on dotnet-runtime-perf run. |
All the wasm jobs passed on https://dev.azure.com/dnceng/internal/_build/results?buildId=2087129&view=results . Except for one AOT job that had a timeout during AOT. That does not need to block this PR though. I'll investigate it separately. |
Oh, and looks like that one is on the one possibly bad machine - PERFTIGER200! |
Other failures here are unrelated. Merging. |
dotnet-latest
instead ofdotnet-net7+latest
for running benchmarks. The former only haswasm-tools
workload installed. And is sufficient for net8.0 projects, and would break any projects trying to build for net7.0 .