CCOR-13194 - Switch integration tests to run against sm v4 server and sdkdev for v5 #553
chrishagglund-ship-itpull_request.yml
on: pull_request
linter
17s
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
14 errors and 3 warnings
|
Node.js v22 - integration v5 (shard 1/3)
Failed test were found and 'fail-on-error' option is set to true
|
|
Node.js v22 - integration v5 (shard 1/3)
Process completed with exit code 1.
|
|
WorkflowExecutor › Should run workflow with http task with asyncComplete true:
src/integration-tests/WorkflowExecutor.test.ts#L171
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/WorkflowExecutor.test.ts:171:7
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:36:9)
|
|
Node.js v20 - integration v5 (shard 2/3)
Failed test were found and 'fail-on-error' option is set to true
|
|
WorkflowExecutor Complete Coverage › Workflow Control (pause/resume/terminate/restart/retry) › pause and resume should work on a running workflow:
src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to register task definitions
at handleSdkError (src/sdk/helpers/errors.ts:49:11)
at MetadataClient.registerTasks (src/sdk/clients/metadata/MetadataClient.ts:64:21)
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:72:5)
|
|
WorkflowExecutor Complete Coverage › Correlation IDs › getByCorrelationIds should return workflows by correlation:
src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to register task definitions
at handleSdkError (src/sdk/helpers/errors.ts:49:11)
at MetadataClient.registerTasks (src/sdk/clients/metadata/MetadataClient.ts:64:21)
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:72:5)
|
|
WorkflowExecutor Complete Coverage › Execution Info › search should find the workflow:
src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to start workflow: No such workflow found by name: jsSdkTest-simpleWf-1779994758820, version: 1
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.complete.test.ts:210:20)
|
|
WorkflowExecutor Complete Coverage › Execution Info › search should find the workflow:
src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to register task definitions
at handleSdkError (src/sdk/helpers/errors.ts:49:11)
at MetadataClient.registerTasks (src/sdk/clients/metadata/MetadataClient.ts:64:21)
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:72:5)
|
|
WorkflowExecutor Complete Coverage › Execution Info › getWorkflowStatus (V4+) › getWorkflowStatus should return status summary:
src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to start workflow: No such workflow found by name: jsSdkTest-simpleWf-1779994758820, version: 1
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.complete.test.ts:210:20)
|
|
WorkflowExecutor Complete Coverage › Execution Info › getWorkflowStatus (V4+) › getWorkflowStatus should return status summary:
src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to register task definitions
at handleSdkError (src/sdk/helpers/errors.ts:49:11)
at MetadataClient.registerTasks (src/sdk/clients/metadata/MetadataClient.ts:64:21)
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:72:5)
|
|
WorkflowExecutor Complete Coverage › Execution Info › getExecution should return full workflow with tasks:
src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to start workflow: No such workflow found by name: jsSdkTest-simpleWf-1779994758820, version: 1
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.complete.test.ts:210:20)
|
|
WorkflowExecutor Complete Coverage › Execution Info › getExecution should return full workflow with tasks:
src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to register task definitions
at handleSdkError (src/sdk/helpers/errors.ts:49:11)
at MetadataClient.registerTasks (src/sdk/clients/metadata/MetadataClient.ts:64:21)
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:72:5)
|
|
WorkflowExecutor Complete Coverage › Start Methods › startWorkflowByName should start a workflow with direct params:
src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to register task definitions
at handleSdkError (src/sdk/helpers/errors.ts:49:11)
at MetadataClient.registerTasks (src/sdk/clients/metadata/MetadataClient.ts:64:21)
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:72:5)
|
|
WorkflowExecutor Complete Coverage › Start Methods › startWorkflows should start multiple workflows in batch:
src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to register task definitions
at handleSdkError (src/sdk/helpers/errors.ts:49:11)
at MetadataClient.registerTasks (src/sdk/clients/metadata/MetadataClient.ts:64:21)
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:72:5)
|
|
Node.js v20 - integration v4 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 v22 - 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 v20 - 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/
|