Structured resolver errors #6446
PhoebeSzmucermain.yml
on: pull_request
Matrix: Build wasm-tools
Matrix: Test
Matrix: Test the C API
Test (no-hash-maps)
3m 12s
Test with extra Cargo features
2m 19s
Test libdl.so
1m 8s
Test on WebAssembly
5m 15s
Rustfmt
16s
Fuzz
2m 27s
check
2m 48s
Check generated files are up-to-date
1m 9s
doc
1m 56s
clippy
1m 55s
typos
9s
verify-publish
3m 6s
maybe-trigger-tag
0s
Annotations
13 errors and 10 warnings
|
Check generated files are up-to-date
Process completed with exit code 1.
|
|
doc
Process completed with exit code 101.
|
|
Test (ubuntu-latest, msrv, --exclude fuzz-stats --exclude wit-component --exclude wasm-mutate-sta...
Process completed with exit code 101.
|
|
Test (ubuntu-latest, stable, --cfg=debug_check_try_op, -F wasmparser/try-op)
Process completed with exit code 101.
|
|
Test (ubuntu-latest, stable, 1)
Process completed with exit code 101.
|
|
Test (no-hash-maps)
Process completed with exit code 101.
|
|
Test (ubuntu-latest, beta)
Process completed with exit code 101.
|
|
Test (ubuntu-latest, stable)
Process completed with exit code 101.
|
|
Test (ubuntu-latest, nightly-2025-07-16)
Process completed with exit code 101.
|
|
Test (ubuntu-latest, nightly-2026-01-20)
Process completed with exit code 101.
|
|
Test (macos-latest, stable)
Process completed with exit code 101.
|
|
Test (windows-latest, stable)
Process completed with exit code 101.
|
|
Record the result of testing and building steps
Process completed with exit code 1.
|
|
Build wasm-tools (wasm32-wasip1, ubuntu-latest, wasm32-wasip1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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 wasm-tools (aarch64-macos, macos-latest, aarch64-apple-darwin, 10.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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 wasm-tools (x86_64-macos, macos-latest, x86_64-apple-darwin, 10.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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 wasm-tools (riscv64-linux, ubuntu-latest, riscv64gc-unknown-linux-gnu, ./ci/docker/riscv64-...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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 wasm-tools (x86_64-linux, ubuntu-latest, x86_64-unknown-linux-gnu, ./ci/docker/x86_64-linux...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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 wasm-tools (aarch64-linux, ubuntu-latest, aarch64-unknown-linux-gnu, ./ci/docker/aarch64-li...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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 wasm-tools (x86_64-musl, ubuntu-latest, x86_64-unknown-linux-musl, ./ci/docker/x86_64-musl/...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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 wasm-tools (aarch64-musl, ubuntu-latest, aarch64-unknown-linux-musl, ./ci/docker/aarch64-mu...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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 wasm-tools (aarch64-windows, windows-11-arm, aarch64-pc-windows-msvc, -Ctarget-feature=+crt...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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 wasm-tools (x86_64-windows, windows-latest, x86_64-pc-windows-msvc, -Ctarget-feature=+crt-s...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
bins-aarch64-linux
|
5.54 MB |
sha256:f68f5ccda32e48b3a65f3db9845e33754cb14d1b21be302eb87600e03203b308
|
|
|
bins-aarch64-macos
|
5.02 MB |
sha256:671d5aa9c97d59953219c0c8d31ea1ea263bd16f847645577222c5f1ce13d982
|
|
|
bins-aarch64-musl
|
5.59 MB |
sha256:6f5ddb794b981b016578308655c3ad354bddafbc6a8e106e2808a0a838c21fec
|
|
|
bins-aarch64-windows
|
3.99 MB |
sha256:cf75d77147f8aed3baf09cf7f4eaff3a8b9ba8697b0befde9efa210e6efc1655
|
|
|
bins-riscv64-linux
|
5.86 MB |
sha256:eb1b2064d8db7eca26b745828f7b8d813a87e741c840fdcee2758ceb967a3da1
|
|
|
bins-wasm32-wasip1
|
3.57 MB |
sha256:2b233f93c016918cf12eb5a22c8c8b2af3c22c84b06aa4ffbf54178c8da533c1
|
|
|
bins-x86_64-linux
|
5.55 MB |
sha256:c26e8286613f20a5850169e61506f7897d91f65f7dea16327b810f7533344850
|
|
|
bins-x86_64-macos
|
5.37 MB |
sha256:75da13d0e15451064e018602664829a80483776753a96c6aa87240c2e6a4fd53
|
|
|
bins-x86_64-musl
|
5.79 MB |
sha256:a858696deb56017aa1d651e986447497622c92be98081a19e6e4fe7f9438250c
|
|
|
bins-x86_64-windows
|
4.31 MB |
sha256:c6c2a0be332562e02ba7d1511fabf5c6ffeb736d3f14ed386c50d3bf3fe94495
|
|