Build and run tests #962
chrisgitiotabuild-and-test.yml
on: schedule
check-for-run-condition
2s
Matrix: build-wasm / build-wasm
Matrix: test-wasm-browser
Matrix: test-wasm
Matrix: build-and-test
Annotations
21 errors and 9 warnings
|
build-and-test (macos-latest)
Process completed with exit code 2.
|
|
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)
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.
|
|
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. 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. 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. 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. 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.
|
|
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. 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. 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. 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 (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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 | |
|---|---|---|---|
|
iota-server-logs-build-and-test-linux-23416799494-962-1.log
Expired
|
274 KB |
sha256:0569eaecc002c38b8a26073a23b80ef0b7e9565579144f64ece2ff5a216db52b
|
|
|
iotaledger~notarization~31C9VP.dockerbuild
|
23.1 KB |
sha256:b59156cc6e9bf8f6722aa8d39f2235667024284f5945958591b624edc682985c
|
|
|
iotaledger~notarization~C2GR6D.dockerbuild
|
22.9 KB |
sha256:d7c2a268a538acf4801a07fd664c59b02a943fa497f82c6b19759c0816736c19
|
|
|
notarization-wasm-bindings-build
Expired
|
3.4 MB |
sha256:291065ec5e102c940d7966ffcd3ed274823155e4950d7a7ad68ea1eb465c5a52
|
|