Test ci integration on sdkdev and sm #547
chrishagglund-ship-itpull_request.yml
on: pull_request
linter
12s
Matrix: integration-tests-v4-sm
Matrix: integration-tests-v4
Matrix: integration-tests-v5-sdkdev
Matrix: integration-tests-v5-sm
Matrix: integration-tests
Matrix: unit-tests
Annotations
33 errors and 7 warnings
|
Node.js v24 - integration v5 sm (shard 1/3)
Failed test were found and 'fail-on-error' option is set to true
|
|
Node.js v24 - integration v5 sm (shard 1/3)
Process completed with exit code 1.
|
|
Node.js v20 - integration v5 (shard 1/3)
Failed test were found and 'fail-on-error' option is set to true
|
|
WorkflowExecutor › Execute with Return Strategy and Consistency › Execute Workflow with Return Strategies and Consistency Levels › Should execute complex workflow with DURABLE + BLOCKING_TASK:
src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to execute workflow
at handleSdkError (src/sdk/helpers/errors.ts:49:11)
at WorkflowExecutor.executeWorkflow (src/sdk/clients/workflow/WorkflowExecutor.ts:170:21)
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:622:26)
|
|
WorkflowExecutor › Execute with Return Strategy and Consistency › Execute Workflow with Return Strategies and Consistency Levels › Should execute complex workflow with DURABLE + BLOCKING_WORKFLOW:
src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to execute workflow
at handleSdkError (src/sdk/helpers/errors.ts:49:11)
at WorkflowExecutor.executeWorkflow (src/sdk/clients/workflow/WorkflowExecutor.ts:170:21)
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:622:26)
|
|
WorkflowExecutor › Execute with Return Strategy and Consistency › Execute Workflow with Return Strategies and Consistency Levels › Should execute complex workflow with DURABLE + TARGET_WORKFLOW:
src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to signal workflow
at handleSdkError (src/sdk/helpers/errors.ts:49:11)
at WorkflowExecutor.signal (src/sdk/clients/workflow/WorkflowExecutor.ts:661:21)
at signalWithRetry (src/integration-tests/WorkflowExecutor.test.ts:698:17)
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:713:11)
|
|
WorkflowExecutor › Should run workflow with http task with asyncComplete true:
src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to update task 'jsSdkTest-http_task_with_asyncComplete_true-1779480296079' result for workflow '80e666a5-5619-11f1-9085-063f86a426d7'
at handleSdkError (src/sdk/helpers/errors.ts:49:11)
at TaskClient.updateTaskResult (src/sdk/clients/task/TaskClient.ts:101:21)
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:217:5)
|
|
WorkflowExecutor › Should return workflow status detail:
src/integration-tests/WorkflowExecutor.test.ts#L158
expect(received).toBeDefined()
Received: undefined
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:158:25)
|
|
WorkflowExecutor › V4+ features › Should be able to get workflow execution status:
src/integration-tests/WorkflowExecutor.test.ts#L124
expect(received).toBeDefined()
Received: undefined
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:124:25)
|
|
WorkflowExecutor › Should be able to start a workflow:
src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to start workflow
at handleSdkError (src/sdk/helpers/errors.ts:49:11)
at WorkflowExecutor.startWorkflow (src/sdk/clients/workflow/WorkflowExecutor.ts:110:21)
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:101:19)
|
|
EventClient › Tag Management › Should get tags for an event handler:
src/integration-tests/EventClient.test.ts#L314
expect(received).toBeGreaterThanOrEqual(expected)
Expected: >= 3
Received: 0
at Object.<anonymous> (src/integration-tests/EventClient.test.ts:314:36)
|
|
EventClient › Event Handler Management › Should remove an event handler:
src/integration-tests/EventClient.test.ts#L279
expect(received).resolves.not.toThrow()
Received promise rejected instead of resolved
Rejected to value: [[Conductor SDK Error]: Failed to remove event handler: jsSdkTest:event-handler:1779480290194: EventHandler with name jsSdkTest:event-handler:1779480290194 not found!]
at expect (node_modules/expect/build/index.js:2116:15)
at Object.<anonymous> (src/integration-tests/EventClient.test.ts:279:19)
|
|
EventClient › Event Handler Management › Should get event handlers for a specific event:
src/integration-tests/EventClient.test.ts#L250
expect(received).toBeDefined()
Received: undefined
at Object.<anonymous> (src/integration-tests/EventClient.test.ts:250:28)
|
|
Node.js v24 - integration v5 (shard 1/3)
Failed test were found and 'fail-on-error' option is set to true
|
|
WorkflowExecutor › Execute with Return Strategy and Consistency › Execute Workflow with Return Strategies and Consistency Levels › Should execute complex workflow with DURABLE + BLOCKING_TASK_INPUT:
src/integration-tests/WorkflowExecutor.test.ts#L303
thrown: "Exceeded timeout of 30000 ms for a hook.
Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout."
at src/integration-tests/WorkflowExecutor.test.ts:303:14
at src/integration-tests/WorkflowExecutor.test.ts:284:21
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:35:9)
|
|
WorkflowExecutor › Execute with Return Strategy and Consistency › Execute Workflow with Return Strategies and Consistency Levels › Should execute complex workflow with DURABLE + BLOCKING_TASK:
src/integration-tests/WorkflowExecutor.test.ts#L303
thrown: "Exceeded timeout of 30000 ms for a hook.
Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout."
at src/integration-tests/WorkflowExecutor.test.ts:303:14
at src/integration-tests/WorkflowExecutor.test.ts:284:21
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:35:9)
|
|
WorkflowExecutor › Execute with Return Strategy and Consistency › Execute Workflow with Return Strategies and Consistency Levels › Should execute complex workflow with DURABLE + BLOCKING_WORKFLOW:
src/integration-tests/WorkflowExecutor.test.ts#L303
thrown: "Exceeded timeout of 30000 ms for a hook.
Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout."
at src/integration-tests/WorkflowExecutor.test.ts:303:14
at src/integration-tests/WorkflowExecutor.test.ts:284:21
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:35:9)
|
|
WorkflowExecutor › Execute with Return Strategy and Consistency › Execute Workflow with Return Strategies and Consistency Levels › Should execute complex workflow with DURABLE + TARGET_WORKFLOW:
src/integration-tests/WorkflowExecutor.test.ts#L303
thrown: "Exceeded timeout of 30000 ms for a hook.
Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout."
at src/integration-tests/WorkflowExecutor.test.ts:303:14
at src/integration-tests/WorkflowExecutor.test.ts:284:21
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:35:9)
|
|
WorkflowExecutor › Execute with Return Strategy and Consistency › Execute Workflow with Return Strategies and Consistency Levels › Should execute complex workflow with SYNC + BLOCKING_TASK_INPUT:
src/integration-tests/WorkflowExecutor.test.ts#L303
thrown: "Exceeded timeout of 30000 ms for a hook.
Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout."
at src/integration-tests/WorkflowExecutor.test.ts:303:14
at src/integration-tests/WorkflowExecutor.test.ts:284:21
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:35:9)
|
|
WorkflowExecutor › Execute with Return Strategy and Consistency › Execute Workflow with Return Strategies and Consistency Levels › Should execute complex workflow with SYNC + BLOCKING_TASK:
src/integration-tests/WorkflowExecutor.test.ts#L303
thrown: "Exceeded timeout of 30000 ms for a hook.
Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout."
at src/integration-tests/WorkflowExecutor.test.ts:303:14
at src/integration-tests/WorkflowExecutor.test.ts:284:21
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:35:9)
|
|
WorkflowExecutor › Execute with Return Strategy and Consistency › Execute Workflow with Return Strategies and Consistency Levels › Should execute complex workflow with SYNC + BLOCKING_WORKFLOW:
src/integration-tests/WorkflowExecutor.test.ts#L303
thrown: "Exceeded timeout of 30000 ms for a hook.
Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout."
at src/integration-tests/WorkflowExecutor.test.ts:303:14
at src/integration-tests/WorkflowExecutor.test.ts:284:21
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:35:9)
|
|
WorkflowExecutor › Execute with Return Strategy and Consistency › Execute Workflow with Return Strategies and Consistency Levels › Should execute complex workflow with SYNC + TARGET_WORKFLOW and validate all aspects:
src/integration-tests/WorkflowExecutor.test.ts#L303
thrown: "Exceeded timeout of 30000 ms for a hook.
Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout."
at src/integration-tests/WorkflowExecutor.test.ts:303:14
at src/integration-tests/WorkflowExecutor.test.ts:284:21
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:35:9)
|
|
EventClient › Event Executions and Statistics › Should get all active event handlers (execution view):
src/integration-tests/EventClient.test.ts#L649
expect(received).toBeGreaterThan(expected)
Expected: > 0
Received: 0
at Object.<anonymous> (src/integration-tests/EventClient.test.ts:649:38)
|
|
EventClient › Event Processing › Should handle incoming event:
src/integration-tests/EventClient.test.ts#L572
expect(received).toBe(expected) // Object.is equality
Expected: true
Received: undefined
at Object.<anonymous> (src/integration-tests/EventClient.test.ts:572:40)
|
|
Node.js v22 - integration v5 sdkdev (shard 1/3)
Failed test were found and 'fail-on-error' option is set to true
|
|
Node.js v22 - integration v5 sdkdev (shard 1/3)
Process completed with exit code 1.
|
|
SDK Worker Registration › update-v2 endpoint verification › SDK detects and uses /api/tasks/update-v2 on v5 server:
src/integration-tests/WorkerRegistration.test.ts#L689
thrown: "Exceeded timeout of 60000 ms for a test.
Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout."
at src/integration-tests/WorkerRegistration.test.ts:689:9
at src/integration-tests/WorkerRegistration.test.ts:688:21
at Object.<anonymous> (src/integration-tests/WorkerRegistration.test.ts:25:9)
|
|
Node.js v22 - integration v5 (shard 2/3)
Failed test were found and 'fail-on-error' option is set to true
|
|
Node.js v22 - integration v5 (shard 2/3)
Process completed with exit code 1.
|
|
AuthorizationClient › AuthorizationClient V4+ › Deletion › deleteUser should remove the second user:
src/integration-tests/AuthorizationClient.test.ts#L307
expect(received).resolves.not.toThrow()
Received promise rejected instead of resolved
Rejected to value: [[Conductor SDK Error]: Failed to delete user 'jssdktest_user2_1779480425531': User 'jssdktest_user2_1779480425531' not found]
at expect (node_modules/expect/build/index.js:2116:15)
at Object.<anonymous> (src/integration-tests/AuthorizationClient.test.ts:307:19)
|
|
AuthorizationClient › AuthorizationClient V4+ › Group Management › removeUserFromGroup should remove a single user:
src/integration-tests/AuthorizationClient.test.ts#L201
expect(received).resolves.not.toThrow()
Received promise rejected instead of resolved
Rejected to value: [[Conductor SDK Error]: Failed to remove user 'jssdktest_user2_1779480425531' from group 'jssdktest_group_1779480425531': User 'jssdktest_user2_1779480425531' not found]
at expect (node_modules/expect/build/index.js:2116:15)
at Object.<anonymous> (src/integration-tests/AuthorizationClient.test.ts:201:19)
|
|
AuthorizationClient › AuthorizationClient V4+ › Group Management › addUsersToGroup should add multiple users to the group:
src/integration-tests/AuthorizationClient.test.ts#L195
expect(received).resolves.not.toThrow()
Received promise rejected instead of resolved
Rejected to value: [[Conductor SDK Error]: Failed to add users to group 'jssdktest_group_1779480425531': User 'jssdktest_user2_1779480425531' not found]
at expect (node_modules/expect/build/index.js:2116:15)
at Object.<anonymous> (src/integration-tests/AuthorizationClient.test.ts:195:19)
|
|
AuthorizationClient › AuthorizationClient V4+ › User Management › upsertUser should create a second user:
src/integration-tests/AuthorizationClient.test.ts#L112
thrown: "Exceeded timeout of 60000 ms for a test.
Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout."
at src/integration-tests/AuthorizationClient.test.ts:112:9
at src/integration-tests/AuthorizationClient.test.ts:101:11
at src/integration-tests/AuthorizationClient.test.ts:17:21
at Object.<anonymous> (src/integration-tests/AuthorizationClient.test.ts:16:9)
|
|
Node.js v20 - integration v4 (shard 1/3)
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@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@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/
|
|
Node.js v24 - integration v5 sm (shard 1/3)
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@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@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/
|
|
Node.js v20 - integration v5 (shard 1/3)
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@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@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/
|
|
Node.js v24 - integration v5 (shard 1/3)
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@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@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/
|
|
Node.js v22 - integration v5 sdkdev (shard 1/3)
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@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@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/
|
|
Node.js v22 - integration v5 (shard 2/3)
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@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@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/
|
|
Node.js v20 - integration v5 sdkdev (shard 1/3)
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@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@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/
|