Skip to content
Tests

fix(CON-352): correct body serialization/deserialization for analysis and attachments #120

Sign in to view logs

fix(CON-352): correct body serialization/deserialization for analysis and attachments

fix(CON-352): correct body serialization/deserialization for analysis and attachments #120

Triggered via pull request March 23, 2026 05:35
@pavanputhrapavanputhra
opened #39
fix/CON-352-body-serialization-deserialization
Status Failure
Total duration 1m 13s
Artifacts –

test.yml

on: pull_request
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 2 warnings
test (20)
Process completed with exit code 1.
tests/search-count-limit.test.ts > Search Count Limit Validation > searchVCons - count integration > should not be limited to 1000 rows when fetching results: tests/search-count-limit.test.ts#L270
Error: Test timed out in 5000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ tests/search-count-limit.test.ts:270:5
tests/new-tools-resources.test.ts > Resources Endpoint Tests > Derived resource endpoints > should return tags derived resource: tests/new-tools-resources.test.ts#L638
AssertionError: expected { '': '' } to deeply equal { department: 'sales', …(2) } - Expected + Received { - "department": "sales", - "priority": "high", - "status": "open", + "": "", } ❯ tests/new-tools-resources.test.ts:638:36
test (18)
The strategy configuration was canceled because "test._20" failed
test (18)
Process completed with exit code 1.
tests/search-count-limit.test.ts > Search Count Limit Validation > searchVCons - count integration > should not be limited to 1000 rows when fetching results: tests/search-count-limit.test.ts#L270
Error: Test timed out in 5000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ tests/search-count-limit.test.ts:270:5
tests/new-tools-resources.test.ts > Resources Endpoint Tests > Derived resource endpoints > should return tags derived resource: tests/new-tools-resources.test.ts#L638
AssertionError: expected { '': '' } to deeply equal { department: 'sales', …(2) } - Expected + Received { - "department": "sales", - "priority": "high", - "status": "open", + "": "", } ❯ tests/new-tools-resources.test.ts:638:36
test (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. 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 (18)
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. 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/