Skip to content

ci: add riscv64-linux build via cross-compilation on ubuntu-24.04 #1151

ci: add riscv64-linux build via cross-compilation on ubuntu-24.04

ci: add riscv64-linux build via cross-compilation on ubuntu-24.04 #1151

Triggered via pull request April 8, 2026 08:11
Status Failure
Total duration 2h 10m 49s
Artifacts 7

main.yml

on: pull_request
Matrix: build
Matrix: build-only-sysroot
Finalize wasi-sdk artifacts
5m 15s
Finalize wasi-sdk artifacts
Test standalone toolchain
3m 30s
Test standalone toolchain
Fit to window
Zoom out
Zoom in

Annotations

1 error and 4 warnings
Finalize wasi-sdk artifacts
Process completed with exit code 1.
Build x86_64-macos
ninja 1.13.2 is already installed and up-to-date. To reinstall 1.13.2, run: brew reinstall ninja
Build arm64-macos
ninja 1.13.2 is already installed and up-to-date. To reinstall 1.13.2, run: brew reinstall ninja
Build x86_64-windows
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@0b201ec74fa43914dc39ae48a89fd1d8cb592756. 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 arm64-windows
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@0b201ec74fa43914dc39ae48a89fd1d8cb592756. 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/

Artifacts

Produced during runtime
Name Size Digest
dist-arm64-linux
135 MB
sha256:ddb2515dac6c3efaabf73ba6fa7b9e6679c6c10d04dbd6b9a1a18a336b744fe6
dist-arm64-macos
125 MB
sha256:a9684d171a455c6691a763c3d122bee4a636fd7721b89daeee39cd9b95fb7d34
dist-arm64-windows
567 MB
sha256:12364e82517a2740cabe2bc0782d983df0f12a30d70790ad74263ca652e1c149
dist-riscv64-linux
63.1 MB
sha256:72ec3a0083a6ffa45c88af2cc5bcc8457174168d1201f0acd242d102342c31eb
dist-x86_64-linux
136 MB
sha256:4bf4b17995375dba66ce932589ec187147f7ec706f4d408109699c1a9b3371ea
dist-x86_64-macos
55.5 MB
sha256:10a4917ef84e1f2d536b05692397658544f18c7e660060ca74b7774738e1489b
dist-x86_64-windows
565 MB
sha256:805392958655b48ffdf9db2e9e0ff0e352d2b60429adb343d04283e10e86e614