-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[test] Try to use nodejs instead of v8 #83524
Conversation
Tagging subscribers to this area: @directhex Issue Detailsnull
|
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
This is speculative jiterp, perhaps we could really enable EH.
does this mean node doesn't have SIMD ? Or has bugs in it ? Or that's our implementation issue which was hidden till now ? |
Might be actual issue, uncovered. I will look at it. For EH, we talked about it with @lewing some time ago. I think we should enable it after p3 branches. |
The |
It is happening on main too, so something might changed recently. I will look again. |
Draft Pull Request was automatically closed for 30 days of inactivity. Please let us know if you'd like to reopen it. |
Draft Pull Request was automatically closed for 30 days of inactivity. Please let us know if you'd like to reopen it. |
No description provided.