[wasm] Move microbenchmarks, and blazor SOD runs to net8.0 by radical · Pull Request #80308 · dotnet/runtime

radical · 2023-01-06T19:41:58Z

Use dotnet-latest instead of dotnet-net7+latest for running benchmarks. The former only has wasm-tools workload installed. And is sufficient for net8.0 projects, and would break any projects trying to build for net7.0 .
Fix up blazor timeout to increase from the default 5mins to 30mins, since the AOT ones (template) are taking longer
Various changes to help with diagnostics, and debugging

ghost · 2023-01-06T19:42:06Z

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

null

Author:	radical
Assignees:	-
Labels:	`arch-wasm`, `perf-pipeline`
Milestone:	-

radical · 2023-01-06T19:42:23Z

/azp run runtime-wasm-perf

azure-pipelines · 2023-01-06T19:42:33Z

Azure Pipelines successfully started running 1 pipeline(s).

radical · 2023-01-06T20:38:52Z

/azp run runtime-wasm-perf

azure-pipelines · 2023-01-06T20:39:05Z

Azure Pipelines successfully started running 1 pipeline(s).

radical · 2023-01-06T22:22:32Z

/azp run runtime-wasm-perf

azure-pipelines · 2023-01-06T22:22:45Z

Azure Pipelines successfully started running 1 pipeline(s).

radical · 2023-01-07T00:18:23Z

/azp run runtime-wasm-perf

azure-pipelines · 2023-01-07T00:18:35Z

Azure Pipelines successfully started running 1 pipeline(s).

radical · 2023-01-07T00:37:26Z

/azp run runtime-wasm-perf

azure-pipelines · 2023-01-07T00:37:35Z

Azure Pipelines successfully started running 1 pipeline(s).

radical · 2023-01-07T00:56:56Z

/azp run runtime-wasm-perf

azure-pipelines · 2023-01-07T00:57:04Z

Azure Pipelines failed to run 1 pipeline(s).

radical · 2023-01-07T01:00:27Z

/azp run runtime-wasm-perf

azure-pipelines · 2023-01-07T01:00:49Z

Azure Pipelines failed to run 1 pipeline(s).

radical · 2023-01-07T01:05:29Z

/azp run runtime-wasm-perf

azure-pipelines · 2023-01-07T01:05:38Z

Azure Pipelines failed to run 1 pipeline(s).

radical · 2023-01-07T01:08:46Z

/azp run runtime-wasm-perf

azure-pipelines · 2023-01-07T01:08:56Z

Azure Pipelines successfully started running 1 pipeline(s).

radical · 2023-01-07T01:15:02Z

/azp run runtime-wasm-perf

azure-pipelines · 2023-01-07T01:15:12Z

Azure Pipelines successfully started running 1 pipeline(s).

radical · 2023-01-07T01:22:25Z

/azp run runtime-wasm-perf

azure-pipelines · 2023-01-07T01:22:34Z

Azure Pipelines successfully started running 1 pipeline(s).

radical · 2023-01-07T01:26:43Z

/azp run runtime-wasm-perf

azure-pipelines · 2023-01-09T18:03:57Z

Azure Pipelines successfully started running 1 pipeline(s).

radical · 2023-01-09T19:41:56Z

/azp run runtime-wasm-perf

azure-pipelines · 2023-01-09T19:42:11Z

Azure Pipelines successfully started running 1 pipeline(s).

radical · 2023-01-09T22:22:11Z

/azp run runtime-wasm-perf

azure-pipelines · 2023-01-09T22:22:21Z

Azure Pipelines successfully started running 1 pipeline(s).

radical · 2023-01-10T23:15:11Z

/azp run runtime-wasm-perf

azure-pipelines · 2023-01-10T23:15:21Z

Azure Pipelines successfully started running 1 pipeline(s).

radical · 2023-01-10T23:26:40Z

/azp run runtime-wasm-perf

azure-pipelines · 2023-01-10T23:26:49Z

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

radical · 2023-01-12T17:03:46Z

Also waiting on dotnet-runtime-perf run.

radical · 2023-01-13T02:36:17Z

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.

radical · 2023-01-13T02:38:50Z

Oh, and looks like that one is on the one possibly bad machine - PERFTIGER200!

radical · 2023-01-13T02:42:12Z

Other failures here are unrelated. Merging.

radical added arch-wasm WebAssembly architecture perf-pipeline Issues with dotnet-runtime-perf, or runtime-wasm-perf pipelines labels Jan 6, 2023

ghost assigned radical Jan 6, 2023

ghost added the area-Infrastructure-mono label Jan 6, 2023

radical changed the title ~~[wasm] test perf branch for 8.0~~[wasm] Move microbenchmarks, and blazor SOD runs to net8.0Jan 6, 2023

build-analysisBot mentioned this pull request Jan 7, 2023
Tracking issue for CI build timeouts #76454
Closed

radical mentioned this pull request Jan 9, 2023
Remove workaround for 8.0 WASM dotnet/performance#2825
Closed

This was referenced Jan 9, 2023
Build fails with "eng/common/tools.sh: line 474: 537 Segmentation fault" #76759
Closed
Test_EventSource_EtwManifestGeneration* tests failing in CI #48798
Closed

radical force-pushed the perf-8 branch from 5084236 to a38ad4eCompare January 10, 2023 05:18

radical marked this pull request as ready for review January 10, 2023 05:24

radical requested review from DrewScoggins, LoopedBard3 and lewing January 10, 2023 23:11

radical force-pushed the perf-8 branch from 09424c1 to 110f3dcCompare January 12, 2023 05:17

radical added 3 commits January 12, 2023 11:15

[wasm] perf: generate, and collect binlogs
040caff

[wasm] perf: remove workaround to allow building for net8.0 with 8.0 sdk
e29d39a

[wasm] perf: revert to using latest v8
2ffcc61
- 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

radical force-pushed the perf-8 branch from 110f3dc to 2ffcc61Compare January 12, 2023 16:17

lewing approved these changes Jan 13, 2023
View reviewed changes

radical merged commit f97f5be into dotnet:mainJan 13, 2023

radical deleted the perf-8 branch January 13, 2023 02:42

ghost locked as resolved and limited conversation to collaborators Feb 12, 2023

Uh oh!

Conversation

radical commented Jan 6, 2023• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ghost commented Jan 6, 2023

Uh oh!

radical commented Jan 6, 2023

Uh oh!

azure-pipelinesBot commented Jan 6, 2023

Uh oh!

radical commented Jan 6, 2023

Uh oh!

azure-pipelinesBot commented Jan 6, 2023

Uh oh!

radical commented Jan 6, 2023

Uh oh!

azure-pipelinesBot commented Jan 6, 2023

Uh oh!

radical commented Jan 7, 2023

Uh oh!

azure-pipelinesBot commented Jan 7, 2023

Uh oh!

radical commented Jan 7, 2023

Uh oh!

azure-pipelinesBot commented Jan 7, 2023

Uh oh!

radical commented Jan 7, 2023

Uh oh!

azure-pipelinesBot commented Jan 7, 2023

Uh oh!

radical commented Jan 7, 2023

Uh oh!

azure-pipelinesBot commented Jan 7, 2023

Uh oh!

radical commented Jan 7, 2023

Uh oh!

azure-pipelinesBot commented Jan 7, 2023

Uh oh!

radical commented Jan 7, 2023

Uh oh!

azure-pipelinesBot commented Jan 7, 2023

Uh oh!

radical commented Jan 7, 2023

Uh oh!

azure-pipelinesBot commented Jan 7, 2023

Uh oh!

radical commented Jan 7, 2023

Uh oh!

azure-pipelinesBot commented Jan 7, 2023

Uh oh!

radical commented Jan 7, 2023

Uh oh!

azure-pipelinesBot commented Jan 9, 2023

Uh oh!

radical commented Jan 9, 2023

Uh oh!

azure-pipelinesBot commented Jan 9, 2023

Uh oh!

radical commented Jan 9, 2023

Uh oh!

azure-pipelinesBot commented Jan 9, 2023

Uh oh!

radical commented Jan 10, 2023

Uh oh!

azure-pipelinesBot commented Jan 10, 2023

Uh oh!

radical commented Jan 10, 2023

Uh oh!

azure-pipelinesBot commented Jan 10, 2023

Uh oh!

radical commented Jan 12, 2023

Uh oh!

radical commented Jan 13, 2023

Uh oh!

radical commented Jan 13, 2023

Uh oh!

radical commented Jan 13, 2023

Uh oh!

Reviewers

radical commented Jan 6, 2023•
edited
Loading