Skip to content

Conversation

@pavelsavara
Copy link
Member

This is second attempt to merge #77449 which was reverted.
On top of previous change I also fix for the different signature on performance.measure API on the V8 and NodeJS shell.

I tested with v8 10.9.130 and V8 10.7.193 and NodeJS v16.13.1.

@ghost
Copy link

ghost commented Nov 2, 2022

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

Issue Details

This is second attempt to merge #77449 which was reverted.
On top of previous change I also fix for the different signature on performance.measure API on the V8 and NodeJS shell.

I tested with v8 10.9.130 and V8 10.7.193 and NodeJS v16.13.1.

Author: pavelsavara
Assignees: pavelsavara
Labels:

arch-wasm, area-System.Runtime.InteropServices.JavaScript

Milestone: 8.0.0

@pavelsavara
Copy link
Member Author

/azp run runtime-wasm

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@radical
Copy link
Member

radical commented Nov 2, 2022

wbt failure: test-main failed early 1 ReferenceError: performance is not defined

@pavelsavara
Copy link
Member Author

/azp run runtime-wasm

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@pavelsavara
Copy link
Member Author

Failures are unrelated.

@pavelsavara pavelsavara merged commit 3b0ef30 into dotnet:main Nov 4, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Dec 4, 2022
@pavelsavara pavelsavara deleted the wasm_browser_profiler_again branch September 2, 2024 15:29
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants