Skip to content
CI

Dev #1238

Sign in to view logs

Dev

Dev #1238

Triggered via pull request April 7, 2026 03:37
@im4codesim4codes
synchronize #2
dev
Status Failure
Total duration 2m 59s
Artifacts 1

ci.yml

on: pull_request
Matrix: unit-tests
Web Tests (Unit)
45s
Web Tests (Unit)
Web Tests (Components)
41s
Web Tests (Components)
Lint
23s
Lint
Typecheck
37s
Typecheck
Secret Scan (gitleaks)
6s
Secret Scan (gitleaks)
Server Unit Tests
46s
Server Unit Tests
Unit Tests (macOS)
2m 32s
Unit Tests (macOS)
Unit Tests (Windows)
55s
Unit Tests (Windows)
Unit Tests (Windows ConPTY)
1m 2s
Unit Tests (Windows ConPTY)
Server DB Integration Tests
43s
Server DB Integration Tests
E2E Tests
E2E Tests
Repo Provider Integration Tests
Repo Provider Integration Tests
Coverage Report
Coverage Report
Docker Build & Push
0s
Docker Build & Push
Android Release Build
0s
Android Release Build
Publish to npm
0s
Publish to npm
Fit to window
Zoom out
Zoom in

Annotations

15 errors and 13 warnings
Unit Tests (Node 22)
Process completed with exit code 1.
test/agent/transport-paths.test.ts > resolveExecutableForSpawn > parses npm .cmd shim and returns (node.exe, [scriptPath]): test/agent/transport-paths.test.ts#L162
AssertionError: expected 'mytool' to contain 'node' Expected: "node" Received: "mytool" ❯ test/agent/transport-paths.test.ts:162:42
test/agent/transport-paths.test.ts > resolveExecutableForSpawn > returns .exe paths unchanged with no prepended args: test/agent/transport-paths.test.ts#L136
AssertionError: expected false to be true // Object.is equality - Expected + Received - true + false ❯ test/agent/transport-paths.test.ts:136:59
test/agent/transport-paths.test.ts > resolveBinaryOnWindows > prefers .CMD over extensionless Unix shim: test/agent/transport-paths.test.ts#L104
AssertionError: expected false to be true // Object.is equality - Expected + Received - true + false ❯ test/agent/transport-paths.test.ts:104:55
Unit Tests (Node 24)
The strategy configuration was canceled because "unit-tests._22" failed
Unit Tests (Node 24)
Process completed with exit code 1.
test/agent/transport-paths.test.ts > resolveExecutableForSpawn > parses npm .cmd shim and returns (node.exe, [scriptPath]): test/agent/transport-paths.test.ts#L162
AssertionError: expected 'mytool' to contain 'node' Expected: "node" Received: "mytool" ❯ test/agent/transport-paths.test.ts:162:42
test/agent/transport-paths.test.ts > resolveExecutableForSpawn > returns .exe paths unchanged with no prepended args: test/agent/transport-paths.test.ts#L136
AssertionError: expected false to be true // Object.is equality - Expected + Received - true + false ❯ test/agent/transport-paths.test.ts:136:59
test/agent/transport-paths.test.ts > resolveBinaryOnWindows > prefers .CMD over extensionless Unix shim: test/agent/transport-paths.test.ts#L104
AssertionError: expected false to be true // Object.is equality - Expected + Received - true + false ❯ test/agent/transport-paths.test.ts:104:55
Unit Tests (Node 20)
The strategy configuration was canceled because "unit-tests._22" failed
Unit Tests (Node 20)
The operation was canceled.
Unit Tests (macOS)
Process completed with exit code 1.
test/agent/transport-paths.test.ts > resolveExecutableForSpawn > parses npm .cmd shim and returns (node.exe, [scriptPath]): test/agent/transport-paths.test.ts#L162
AssertionError: expected 'mytool' to contain 'node' Expected: "node" Received: "mytool" ❯ test/agent/transport-paths.test.ts:162:42
test/agent/transport-paths.test.ts > resolveExecutableForSpawn > returns .exe paths unchanged with no prepended args: test/agent/transport-paths.test.ts#L136
AssertionError: expected false to be true // Object.is equality - Expected + Received - true + false ❯ test/agent/transport-paths.test.ts:136:59
test/agent/transport-paths.test.ts > resolveBinaryOnWindows > prefers .CMD over extensionless Unix shim: test/agent/transport-paths.test.ts#L104
AssertionError: expected false to be true // Object.is equality - Expected + Received - true + false ❯ test/agent/transport-paths.test.ts:104:55
Secret Scan (gitleaks)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, gitleaks/gitleaks-action@v2. 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/
Lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@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/
Typecheck
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@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/
Server DB Integration Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@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/
Web Tests (Unit)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@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/
Unit Tests (Windows)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@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/
Server Unit Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@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/
Unit Tests (Windows ConPTY)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@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/
Web Tests (Components)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@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/
Unit Tests (Node 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@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/
Unit Tests (Node 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@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/
Unit Tests (Node 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@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/
Unit Tests (macOS)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@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
gitleaks-results.sarif
367 Bytes
sha256:515c453da9768c680272a04af1265b912fe6926b0cafb5485bbc316654110e3c