Skip to content

Conversation

@radical
Copy link
Member

@radical radical commented Nov 1, 2022

This reverts commit 0e24ea7.

It broke all the perf pipeline wasm builds. It happens with v8 10.9.130:

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).
  • It wasn't caught in the CI checks because those are using an older version of v8.

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).
@ghost
Copy link

ghost commented Nov 1, 2022

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

Issue Details

This reverts commit 0e24ea7.

It broke all the perf pipeline wasm builds. It happens with v8 10.9.130:

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).

Author: radical
Assignees: -
Labels:

arch-wasm, test-failure

Milestone: -

@radical
Copy link
Member Author

radical commented Nov 1, 2022

I'll open a separate PR to use the same version of V8 for all our testing on CI - #66164 .

@radical
Copy link
Member Author

radical commented Nov 1, 2022

/azp run runtime-wasm-perf

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@radical radical added the blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' label Nov 1, 2022
@radical
Copy link
Member Author

radical commented Nov 2, 2022

All the wasm jobs are passing. Merging this now to unblock CI.

@radical radical merged commit d3a3eda into dotnet:main Nov 2, 2022
@radical radical deleted the revert-profiler branch November 2, 2022 02:01
@pavelsavara
Copy link
Member

thanks for this

@pavelsavara
Copy link
Member

It's interesting. They added the performance.measure API in minor update, it's not in the 10.7.193
It's also interesting they use NodeJS shape of the API.

Here is another attempt #77779

@ghost ghost locked as resolved and limited conversation to collaborators Dec 2, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

arch-wasm WebAssembly architecture area-Build-mono blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' test-failure

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants