After Bug 1624266, all the js ref tests that use `SharedArrayBuffer` are expected to fail. It's because now we use `global.crossOriginIsolated` to decide if the constructor of the `SharedArrayBuffer` is exposed or not. Also, from https://bugzilla.mozilla.org/show_bug.cgi?id=1624266#c43, all these tests are running in a browser on the treeherder and thus break the current check inside the test (for instance: https://searchfox.org/mozilla-central/rev/54f965e51e4f77866bec42737978d40d4c1fdfc5/js/src/tests/test262/built-ins/ArrayBuffer/prototype/byteLength/this-is-sharedarraybuffer.js#1). A solution is to run these tests with COOP+COEP headers, so that `global.crossOriginIsolated` would be `true` and thus the constructor of the `SharedArrayBuffer` is exposed.
Bug 1635176 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
After Bug 1624266, all the js ref tests that use `SharedArrayBuffer` are expected to fail. It's because now we use `global.crossOriginIsolated` to decide if the constructor of the `SharedArrayBuffer` is exposed or not. Also, from https://bugzilla.mozilla.org/show_bug.cgi?id=1624266#c43, all these tests are running in a browser on the treeherder and thus break the current check inside the test (for instance: https://searchfox.org/mozilla-central/rev/54f965e51e4f77866bec42737978d40d4c1fdfc5/js/src/tests/test262/built-ins/ArrayBuffer/prototype/byteLength/this-is-sharedarraybuffer.js#1). A solution is to run these tests with COOP+COEP headers, so that `global.crossOriginIsolated` would be `true` and thus the constructor of the `SharedArrayBuffer` is exposed. Edited: Once the fix is applied, [this change](https://phabricator.services.mozilla.com/D73260) should be reverted as well.