Skip to content

Build and run tests #1045

Build and run tests

Build and run tests #1045

Triggered via schedule April 3, 2026 00:55
Status Failure
Total duration 14m 8s
Artifacts 3

build-and-test.yml

on: schedule
check-for-run-condition
2s
check-for-run-condition
Matrix: build-wasm / build-wasm
check-for-modification
7s
check-for-modification
Matrix: test-wasm-browser
Matrix: test-wasm
Matrix: build-and-test
Fit to window
Zoom out
Zoom in

Annotations

26 errors and 9 warnings
test-wasm (ubuntu-24.04)
Process completed with exit code 10.
test-wasm-browser (chrome)
Process completed with exit code 1.
test-wasm-browser (chrome)
Cannot find name 'TransactionEffects'. Did you mean 'AnimationEffect'?
test-wasm-browser (chrome)
Cannot find name 'IotaEvent'.
test-wasm-browser (chrome)
Cannot find name 'TransactionEffects'. Did you mean 'AnimationEffect'?
test-wasm-browser (chrome)
Cannot find name 'IotaEvent'.
test-wasm-browser (chrome)
Cannot find name 'TransactionEffects'. Did you mean 'AnimationEffect'?
test-wasm-browser (chrome)
Cannot find module '@iota/iota_interaction_ts/http_client' or its corresponding type declarations.
test-wasm-browser (chrome)
Module '"./index"' has no exported member 'CoreClientReadOnly'.
test-wasm-browser (chrome)
Module '"./index"' has no exported member 'CoreClient'.
test-wasm-browser (chrome)
Cannot find module './iota_client_helpers' or its corresponding type declarations.
test-wasm-browser (chrome)
Cannot find module './iota_interaction_ts.js' or its corresponding type declarations.
test-wasm-browser (firefox)
Process completed with exit code 1.
test-wasm-browser (firefox)
Cannot find name 'TransactionEffects'. Did you mean 'AnimationEffect'?
test-wasm-browser (firefox)
Cannot find name 'IotaEvent'.
test-wasm-browser (firefox)
Cannot find name 'TransactionEffects'. Did you mean 'AnimationEffect'?
test-wasm-browser (firefox)
Cannot find name 'IotaEvent'.
test-wasm-browser (firefox)
Cannot find name 'TransactionEffects'. Did you mean 'AnimationEffect'?
test-wasm-browser (firefox)
Cannot find module '@iota/iota_interaction_ts/http_client' or its corresponding type declarations.
test-wasm-browser (firefox)
Module '"./index"' has no exported member 'CoreClientReadOnly'.
test-wasm-browser (firefox)
Module '"./index"' has no exported member 'CoreClient'.
test-wasm-browser (firefox)
Cannot find module './iota_client_helpers' or its corresponding type declarations.
test-wasm-browser (firefox)
Cannot find module './iota_interaction_ts.js' or its corresponding type declarations.
build-and-test (windows-latest)
Process completed with exit code 127.
build-and-test (macos-latest)
Process completed with exit code 101.
build-and-test (ubuntu-24.04)
Process completed with exit code 101.
check-for-modification
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. 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 / build-wasm (ubuntu-latest)
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@v3, actions/setup-node@v1, actions/upload-artifact@v4, jetli/wasm-bindgen-action@24ba6f9fff570246106ac3f80f35185600c3f6c9. 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-wasm (ubuntu-24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/download-artifact@v4, actions/setup-node@v1. 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-wasm-browser (chrome)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/download-artifact@v4, actions/setup-node@v1, docker/build-push-action@v6.2.0. 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-wasm-browser (firefox)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/download-artifact@v4, actions/setup-node@v1, docker/build-push-action@v6.2.0. 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 (windows-latest)
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@v3. 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 (macos-latest)
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@v3. 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 (macos-latest)
postgresql@14 has been deprecated because it is not supported upstream! It will be disabled on 2026-11-12.
build-and-test (ubuntu-24.04)
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@v3. 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
iotaledger~notarization~PZADH6.dockerbuild
21.9 KB
sha256:de40fb6a118834ba86b22ce927db50926b086048f2d99bd812a82c983cd0e85e
iotaledger~notarization~RTDS8U.dockerbuild
22.5 KB
sha256:2139cd98ce1eb698b63f33677df07a0c0b85318ed000d884d6f45e2c68193140
notarization-wasm-bindings-build Expired
3.39 MB
sha256:5c4a8617117bcb99f94d7d2799c78253e6aede203007dc03b1ed05242efa7c2e