Support SharedArrayBuffer in WASM Memory #2395
Triggered via pull request
February 5, 2025 07:48
Status
Failure
Total duration
1h 9m 6s
Artifacts
–
es-actions.yml
on: pull_request
check-tidy
56s
build-on-macos
13m 40s
build-on-macos-arm64
4m 39s
build-by-clang
5m 22s
build-on-windows-x64-uwp-x86-shared
6m 35s
build-test-on-x86-x64-debug
34m 51s
build-test-on-self-hosted-linux
22m 2s
build-test-on-self-hosted-arm-linux
13m 54s
build-test-on-self-hosted-arm64-linux
13m 34s
build-test-on-riscv64-release
29m 3s
build-test-debugger
4m 0s
build-test-api
3m 43s
build-test-codecache
16m 46s
build-test-wasmjs
1h 4m
Matrix: build-test-on-android
Matrix: build-test-on-x64-release
Matrix: build-test-on-x86-release
Matrix: test-on-windows-clang-cl
Matrix: test-on-windows-x86-x64
Annotations
2 errors and 12 warnings
build-test-wasmjs
The action 'Run mxschmitt/action-tmate@v3' has timed out after 60 minutes.
|
build-test-wasmjs
Process completed with exit code 1.
|
build-on-macos-arm64
icu4c@76 76.1_1 is already installed and up-to-date.
To reinstall 76.1_1, run:
brew reinstall icu4c@76
|
build-on-macos
icu4c@76 76.1_1 is already installed and up-to-date.
To reinstall 76.1_1, run:
brew reinstall icu4c@76
|
build-test-wasmjs
No public SSH keys found for clover2123; continuing without them even if it is less secure (please consider adding an SSH key, see https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)
|
build-test-wasmjs
No public SSH keys found for clover2123; continuing without them even if it is less secure (please consider adding an SSH key, see https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)
|
build-test-wasmjs
No public SSH keys found for clover2123; continuing without them even if it is less secure (please consider adding an SSH key, see https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)
|
build-test-wasmjs
No public SSH keys found for clover2123; continuing without them even if it is less secure (please consider adding an SSH key, see https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)
|
build-test-wasmjs
No public SSH keys found for clover2123; continuing without them even if it is less secure (please consider adding an SSH key, see https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)
|
build-test-wasmjs
No public SSH keys found for clover2123; continuing without them even if it is less secure (please consider adding an SSH key, see https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)
|
build-test-wasmjs
No public SSH keys found for clover2123; continuing without them even if it is less secure (please consider adding an SSH key, see https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)
|
build-test-wasmjs
No public SSH keys found for clover2123; continuing without them even if it is less secure (please consider adding an SSH key, see https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)
|
build-test-wasmjs
No public SSH keys found for clover2123; continuing without them even if it is less secure (please consider adding an SSH key, see https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)
|
build-test-wasmjs
No public SSH keys found for clover2123; continuing without them even if it is less secure (please consider adding an SSH key, see https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)
|