Optimize wasm by default on contract build #10445
fnandorust.yml
on: pull_request
Matrix: build-and-test-macos
Matrix: build-and-test-windows
Matrix: build-and-test
Matrix: cargo-deny
Matrix: publish-dry-run
Waiting for pending jobs
check
4m 44s
complete
3s
Annotations
10 errors and 5 warnings
|
build-and-test (msrv, ubuntu-jammy-8-cores-arm64, aarch64-unknown-linux-gnu)
Canceling since a higher priority waiting request for Rust-refs/pull/2581/merge exists
|
|
build-and-test (msrv, ubuntu-jammy-8-cores-arm64, aarch64-unknown-linux-gnu)
The operation was canceled.
|
|
build-and-test (latest, ubuntu-jammy-8-cores-arm64, aarch64-unknown-linux-gnu)
Canceling since a higher priority waiting request for Rust-refs/pull/2581/merge exists
|
|
build-and-test (latest, ubuntu-jammy-8-cores-arm64, aarch64-unknown-linux-gnu)
The operation was canceled.
|
|
build-and-test (msrv, ubuntu-latest-8-cores, x86_64-unknown-linux-gnu)
Canceling since a higher priority waiting request for Rust-refs/pull/2581/merge exists
|
|
build-and-test (msrv, ubuntu-latest-8-cores, x86_64-unknown-linux-gnu)
The operation was canceled.
|
|
build-and-test (latest, ubuntu-latest-8-cores, x86_64-unknown-linux-gnu)
Canceling since a higher priority waiting request for Rust-refs/pull/2581/merge exists
|
|
build-and-test (latest, ubuntu-latest-8-cores, x86_64-unknown-linux-gnu)
The operation was canceled.
|
|
complete
Process completed with exit code 1.
|
|
Rust
Canceling since a higher priority waiting request for Rust-refs/pull/2581/merge exists
|
|
check
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 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-and-test (msrv, ubuntu-jammy-8-cores-arm64, aarch64-unknown-linux-gnu)
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 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-and-test (latest, ubuntu-jammy-8-cores-arm64, aarch64-unknown-linux-gnu)
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 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-and-test (msrv, ubuntu-latest-8-cores, x86_64-unknown-linux-gnu)
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 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-and-test (latest, ubuntu-latest-8-cores, x86_64-unknown-linux-gnu)
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 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/
|