[jspi] Remove module splitting changes. (#8529) #18581
ci.yml
on: push
lint
0s
clang (LTO)
20m 4s
clang with fuzztest
1m 4s
asan
0s
alpine
11m 31s
ubsan
0s
tsan
0s
emscripten
3m 12s
mingw
2m 32s
c++20
8m 3s
noasserts
0s
Matrix: build
Annotations
20 errors and 7 warnings
|
tsan
Canceling since a higher priority waiting request for CI-refs/heads/main exists
|
|
build (ubuntu-latest)
Canceling since a higher priority waiting request for CI-refs/heads/main exists
|
|
clang (LTO)
Canceling since a higher priority waiting request for CI-refs/heads/main exists
|
|
asan
Canceling since a higher priority waiting request for CI-refs/heads/main exists
|
|
noasserts
Canceling since a higher priority waiting request for CI-refs/heads/main exists
|
|
ubsan
Canceling since a higher priority waiting request for CI-refs/heads/main exists
|
|
build (ubuntu-22.04)
Canceling since a higher priority waiting request for CI-refs/heads/main exists
|
|
build (windows-11-arm)
Canceling since a higher priority waiting request for CI-refs/heads/main exists
|
|
build (windows-latest)
Canceling since a higher priority waiting request for CI-refs/heads/main exists
|
|
mingw
Canceling since a higher priority waiting request for CI-refs/heads/main exists
|
|
mingw
The operation was canceled.
|
|
clang with fuzztest
Canceling since a higher priority waiting request for CI-refs/heads/main exists
|
|
clang with fuzztest
The operation was canceled.
|
|
emscripten
Canceling since a higher priority waiting request for CI-refs/heads/main exists
|
|
emscripten
The operation was canceled.
|
|
c++20
Canceling since a higher priority waiting request for CI-refs/heads/main exists
|
|
build (macos-latest)
Canceling since a higher priority waiting request for CI-refs/heads/main exists
|
|
c++20
The operation was canceled.
|
|
build (macos-latest)
The operation was canceled.
|
|
CI
Canceling since a higher priority waiting request for CI-refs/heads/main exists
|
|
alpine
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
mingw
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
clang with fuzztest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
emscripten
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
c++20
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build (macos-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build (macos-latest)
ninja 1.13.2 is already installed and up-to-date.
To reinstall 1.13.2, run:
brew reinstall ninja
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
build-macos-latest
|
15.6 MB |
sha256:b6513c37dc2bebce4641a02313d69fe93a9e4f58cda4a0c4b9c624666f039395
|
|