-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[wasm] JS Interop tests failing with latest chrome - JavaScript host object 'SharedArrayBuffer' not found
#61945
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue Details#61937 upgrades chrome used to run the tests, to the latest stable version -
|
cc @kg @pavelsavara |
Strangely, this doesn't seem to fail on AOT, or EAT - https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-61937-merge-a4bb0d1fb1df4755bf/System.Private.Runtime.InteropServices.JavaScript.Tests/1/console.dfb115ec.log?sv=2019-07-07& . |
What version of chrome was it previously? They're changing the requirements to access it. https://developer.chrome.com/blog/enabling-shared-array-buffer/ |
We were running with - 84.0.4147.105 |
Then based on that post I linked, this is an expected failure and we need to make policy header changes. I don't know exactly how it works since COEP/COOP/etc headers are a nightmare. It might be as simple as generating the right headers in whatever httpd we use to serve tests. |
I can reproduce it locally. I will have look at xharness http server and see if we could set the headers. |
- Update chrome+chromedriver for helix tests to latest stable (`96.0.4664.45`) - Enable library tests to run on Windows, for manual runs - Disable windows/AOT builds completely due to #61721 - Disable failing WBT tests on windows due to #61725 - Disable JS interop tests failing with new chrome - #61945 Co-authored-by: Radek Doulik <[email protected]>
#61937 upgrades chrome used to run the tests, to the latest stable version -
96.0.4664.45
:Build, and Log
The text was updated successfully, but these errors were encountered: