-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Revert "[wasm] browser profiler (#77449)" #77759
Conversation
This reverts commit 0e24ea7. This breaks with v8 10.9.130 with: ``` Error: Invalid 'startMark' argument: No numeric 'startTime' field at pe (/home/helixbot/work/B2E7090F/w/A520093B/e/performance/artifacts/bin/for-running/MicroBenchmarks/659adab0-5c86-4e74-8913-672bd56fd58e/bin/net7.0/browser-wasm/AppBundle/dotnet.js:3:12994) at /home/helixbot/work/B2E7090F/w/A520093B/e/performance/artifacts/bin/for-running/MicroBenchmarks/659adab0-5c86-4e74-8913-672bd56fd58e/bin/net7.0/browser-wasm/AppBundle/dotnet.js:5:95874 exiting due to exception: Error: Invalid 'startMark' argument: No numeric 'startTime' field ``` It works fine with older versions like `10.7.193` (current stable).
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsThis reverts commit 0e24ea7. It broke all the perf pipeline wasm builds. It happens with v8
It works fine with older versions like
|
I'll open a separate PR to use the same version of V8 for all our testing on CI - #66164 . |
/azp run runtime-wasm-perf |
Azure Pipelines successfully started running 1 pipeline(s). |
All the wasm jobs are passing. Merging this now to unblock CI. |
thanks for this |
It's interesting. They added the Here is another attempt #77779 |
This reverts commit 0e24ea7.
It broke all the perf pipeline wasm builds. It happens with v8
10.9.130
:10.7.193
(current stable).