Skip to content

WebAssembly support via WAMR interpreter #127

WebAssembly support via WAMR interpreter

WebAssembly support via WAMR interpreter #127

Triggered via pull request April 6, 2026 11:35
@dannotedannote
synchronize #3
wasm
Status Failure
Total duration 4m 12s
Artifacts 1

ci.yml

on: pull_request
C static analysis
6s
C static analysis
UBSan + Zig Debug
3m 25s
UBSan + Zig Debug
AddressSanitizer
4m 9s
AddressSanitizer
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

1 error and 15 warnings
test (27.0, 1.18)
Process completed with exit code 14.
C static analysis
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/
test (27.0, 1.18)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, goto-bus-stop/setup-zig@v2. 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/
test (27.0, 1.18): lib/quickbeam/wasm/import_rewriter.ex#L81
Function is too complex (cyclomatic complexity is 11, max is 9).
test (27.0, 1.18): test/wasm_test.exs#L646
Numbers larger than 9999 should be written with underscores: 65_536
test (27.0, 1.18): test/wasm_test.exs#L652
Numbers larger than 9999 should be written with underscores: 65_530
test (27.0, 1.18): lib/quickbeam/wasm.ex#L56
Nested modules could be aliased at the top of the invoking module.
test (27.0, 1.18): lib/quickbeam/wasm.ex#L67
Nested modules could be aliased at the top of the invoking module.
test (27.0, 1.18)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0oprTaQAAAAAMjo/6yrk4T7fP9z+7p4m0UEFPRURHRTA1MTEARWRnZQ==
test (27.0, 1.18)
Failed to restore: Cache service responded with 400
UBSan + Zig Debug
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, goto-bus-stop/setup-zig@v2. 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/
UBSan + Zig Debug
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0oJrTaQAAAABQCv4XkIprTZsrB396l8vWUEFPRURHRTA1MTAARWRnZQ==
UBSan + Zig Debug
Failed to restore: Cache service responded with 400
AddressSanitizer
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4, goto-bus-stop/setup-zig@v2. 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/
AddressSanitizer
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0l5rTaQAAAACd5DWXn8QWSJnXqIxdL1ruUEhMMzBFREdFMDExNwBFZGdl
AddressSanitizer
Failed to restore: Cache service responded with 400

Artifacts

Produced during runtime
Name Size Digest
asan-logs
2.79 KB
sha256:3ad917a59199abc587dedf147c7531a8733477a1164785d954699d02d140b963