Skip to content
CI Main Branch

fix(test): use absolute config path and increase client timeout for CI #443

Sign in to view logs

fix(test): use absolute config path and increase client timeout for CI

fix(test): use absolute config path and increase client timeout for CI #443

Triggered via push March 25, 2026 15:31
@AlexMikhalevAlexMikhalev
pushed 75f9e78
main
Status Failure
Total duration 18m 25s
Artifacts 2

ci-main.yml

on: push
Build Setup
9s
Build Setup
Frontend Build
2m 9s
Frontend Build
WASM Build
29s
WASM Build
Security Scan
13s
Security Scan
Matrix: rust-build
Integration Tests
0s
Integration Tests
Docker Build
0s
Docker Build
Build Summary
5s
Build Summary
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 4 warnings
Rust Build (x86_64-unknown-linux-gnu)
Process completed with exit code 101.
Build Summary
Process completed with exit code 1.
Security Scan
cargo audit found issues or had parsing errors
WASM Build
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, jetli/wasm-pack-action@v0.4.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/
Frontend Build
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/setup-node@v4, 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/
Rust Build (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/download-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
frontend-dist Expired
2.67 MB
sha256:7aa10ababa843b541f118fb03f1571f1e6cb1a07b060c054e9570336252b0d0c
wasm-package Expired
134 KB
sha256:01776c3c1036427f64a6477078fe500d237a03cdba794cd30a0cf8ccc30f1297