Skip to content

Conversation

@radical
Copy link
Member

@radical radical commented Sep 30, 2022

This will fix:
[03:51:52] fail: [out of order message from the browser]: http://127.0.0.1:34655/dotnet.js 13:13768 Uncaught ReferenceError: SharedArrayBuffer is not defined

Fixes #76331 .

@radical radical added arch-wasm WebAssembly architecture area-Build-mono labels Sep 30, 2022
@ghost ghost assigned radical Sep 30, 2022
@ghost
Copy link

ghost commented Sep 30, 2022

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

Issue Details

This will fix:
[03:51:52] fail: [out of order message from the browser]: http://127.0.0.1:34655/dotnet.js 13:13768 Uncaught ReferenceError: SharedArrayBuffer is not defined

Author: radical
Assignees: -
Labels:

arch-wasm, area-Build-mono

Milestone: -

@radical radical requested a review from lambdageek September 30, 2022 03:05
@radical
Copy link
Member Author

radical commented Sep 30, 2022

/azp run runtime-wasm

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@radical
Copy link
Member Author

radical commented Sep 30, 2022

Wasm.Build.Tests failure is #76429 .

@radical radical merged commit 5c8aade into dotnet:main Sep 30, 2022
@radical radical deleted the threading-sample branch September 30, 2022 08:27
@ghost ghost locked as resolved and limited conversation to collaborators Oct 30, 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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

WASM CI failure: Wasm.Browser.Threads.Sample - SharedArrayBuffer is not defined, exit code 71, GENERAL_FAILURE

2 participants