Skip to content

Test ci integration on sdkdev and sm #545

Test ci integration on sdkdev and sm

Test ci integration on sdkdev and sm #545

Status Failure
Total duration 27m 39s
Artifacts

pull_request.yml

on: pull_request
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
Fit to window
Zoom out
Zoom in

Annotations

97 errors and 21 warnings
Node.js v24 - integration v5 (shard 3/3)
Failed test were found and 'fail-on-error' option is set to true
TaskClient Complete Coverage › Task Logs › addTaskLog should add a log entry to a task: src/sdk/createConductorClient/helpers/handleAuth.ts#L65
[Conductor SDK Error]: Failed to generate authorization token: Unknown error (HTTP 503) at getNewToken (src/sdk/createConductorClient/helpers/handleAuth.ts:65:13) at handleAuth (src/sdk/createConductorClient/helpers/handleAuth.ts:123:7) at createConductorClient (src/sdk/createConductorClient/createConductorClient.ts:66:18) at Object.<anonymous> (src/integration-tests/TaskClient.complete.test.ts:44:14)
TaskClient Complete Coverage › Task Queries › getTaskPollData should return poll data: src/sdk/createConductorClient/helpers/handleAuth.ts#L65
[Conductor SDK Error]: Failed to generate authorization token: Unknown error (HTTP 503) at getNewToken (src/sdk/createConductorClient/helpers/handleAuth.ts:65:13) at handleAuth (src/sdk/createConductorClient/helpers/handleAuth.ts:123:7) at createConductorClient (src/sdk/createConductorClient/createConductorClient.ts:66:18) at Object.<anonymous> (src/integration-tests/TaskClient.complete.test.ts:44:14)
TaskClient Complete Coverage › Task Queries › getQueueSizeForTask should return queue sizes: src/sdk/createConductorClient/helpers/handleAuth.ts#L65
[Conductor SDK Error]: Failed to generate authorization token: Unknown error (HTTP 503) at getNewToken (src/sdk/createConductorClient/helpers/handleAuth.ts:65:13) at handleAuth (src/sdk/createConductorClient/helpers/handleAuth.ts:123:7) at createConductorClient (src/sdk/createConductorClient/createConductorClient.ts:66:18) at Object.<anonymous> (src/integration-tests/TaskClient.complete.test.ts:44:14)
TaskClient Complete Coverage › Task Queries › search (V4+) › search should find tasks: src/sdk/createConductorClient/helpers/handleAuth.ts#L65
[Conductor SDK Error]: Failed to generate authorization token: Unknown error (HTTP 503) at getNewToken (src/sdk/createConductorClient/helpers/handleAuth.ts:65:13) at handleAuth (src/sdk/createConductorClient/helpers/handleAuth.ts:123:7) at createConductorClient (src/sdk/createConductorClient/createConductorClient.ts:66:18) at Object.<anonymous> (src/integration-tests/TaskClient.complete.test.ts:44:14)
TaskClient Complete Coverage › Task Queries › getTask should return task details by ID: src/sdk/createConductorClient/helpers/handleAuth.ts#L65
[Conductor SDK Error]: Failed to generate authorization token: Unknown error (HTTP 503) at getNewToken (src/sdk/createConductorClient/helpers/handleAuth.ts:65:13) at handleAuth (src/sdk/createConductorClient/helpers/handleAuth.ts:123:7) at createConductorClient (src/sdk/createConductorClient/createConductorClient.ts:66:18) at Object.<anonymous> (src/integration-tests/TaskClient.complete.test.ts:44:14)
TaskManager › TaskManager workflow execution › Updates single worker properties: src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to register workflow at handleSdkError (src/sdk/helpers/errors.ts:49:11) at WorkflowExecutor.registerWorkflow (src/sdk/clients/workflow/WorkflowExecutor.ts:63:21) at Object.<anonymous> (src/integration-tests/TaskManager.test.ts:427:5)
TaskManager › TaskManager workflow execution › multi worker example: src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to register workflow at handleSdkError (src/sdk/helpers/errors.ts:49:11) at WorkflowExecutor.registerWorkflow (src/sdk/clients/workflow/WorkflowExecutor.ts:63:21) at Object.<anonymous> (src/integration-tests/TaskManager.test.ts:330:5)
TaskManager › TaskManager workflow execution › If no error handler provided. it should just update the task: 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/TaskManager.test.ts:244:5)
TaskManager › TaskManager workflow execution › On error it should call the errorHandler provided: src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to register workflow at handleSdkError (src/sdk/helpers/errors.ts:49:11) at WorkflowExecutor.registerWorkflow (src/sdk/clients/workflow/WorkflowExecutor.ts:63:21) at Object.<anonymous> (src/integration-tests/TaskManager.test.ts:188:5)
ApplicationClient › ApplicationClient V4+ › Access Key Management › Should get app by access key id: src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to create application at handleSdkError (src/sdk/helpers/errors.ts:49:11) at ApplicationClient.createApplication (src/sdk/clients/application/ApplicationClient.ts:55:21) at Object.<anonymous> (src/integration-tests/ApplicationClient.test.ts:233:26)
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 SYNC + BLOCKING_TASK_INPUT: src/integration-tests/WorkflowExecutor.test.ts#L363
Failed to register workflows: [Conductor SDK Error]: Failed to register workflow definition at registerAllWorkflows (src/integration-tests/WorkflowExecutor.test.ts:363:15) at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:309:7)
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#L363
Failed to register workflows: [Conductor SDK Error]: Failed to register workflow definition at registerAllWorkflows (src/integration-tests/WorkflowExecutor.test.ts:363:15) at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:309:7)
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#L363
Failed to register workflows: [Conductor SDK Error]: Failed to register workflow definition at registerAllWorkflows (src/integration-tests/WorkflowExecutor.test.ts:363:15) at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:309:7)
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#L363
Failed to register workflows: [Conductor SDK Error]: Failed to register workflow definition at registerAllWorkflows (src/integration-tests/WorkflowExecutor.test.ts:363:15) at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:309:7)
WorkflowExecutor › Should run workflow with an optional http task: src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to register workflow at handleSdkError (src/sdk/helpers/errors.ts:49:11) at WorkflowExecutor.registerWorkflow (src/sdk/clients/workflow/WorkflowExecutor.ts:63:21) at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:242:5)
WorkflowExecutor › Should run workflow with http task with asyncComplete true: src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to get workflow at handleSdkError (src/sdk/helpers/errors.ts:49:11) at WorkflowExecutor.getWorkflow (src/sdk/clients/workflow/WorkflowExecutor.ts:258:23) at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:207:18)
EventClient › Event Executions and Statistics › Should get event handlers with statistics: src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to handle incoming event at handleSdkError (src/sdk/helpers/errors.ts:49:11) at EventClient.handleIncomingEvent (src/sdk/clients/event/EventClient.ts:113:21) at Object.<anonymous> (src/integration-tests/EventClient.test.ts:756:7)
EventClient › Event Handler Management › Should update an event handler: src/integration-tests/EventClient.test.ts#L206
expect(received).toEqual(expected) // deep equality Expected: false Received: undefined at Object.<anonymous> (src/integration-tests/EventClient.test.ts:206:39)
EventClient › Event Handler Management › Should add multiple event handlers: src/integration-tests/EventClient.test.ts#L174
expect(received).toBeGreaterThanOrEqual(expected) Expected: >= 2 Received: 0 at Object.<anonymous> (src/integration-tests/EventClient.test.ts:174:36)
EventClient › Event Handler Management › Should add a single event handler: src/integration-tests/EventClient.test.ts#L113
expect(received).resolves.not.toThrow() Received promise rejected instead of resolved Rejected to value: [[Conductor SDK Error]: Failed to add event handler] at expect (node_modules/expect/build/index.js:2116:15) at Object.<anonymous> (src/integration-tests/EventClient.test.ts:113:19)
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 › Execute with Return Strategy and Consistency › Execute Workflow with Return Strategies and Consistency Levels › Should execute complex workflow with DURABLE + BLOCKING_TASK_INPUT: 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:624:26)
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:624: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:624: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 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:624:26)
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/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:624:26)
WorkflowExecutor › Execute with Return Strategy and Consistency › Execute Workflow with Return Strategies and Consistency Levels › Should execute complex workflow with SYNC + 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:624:26)
WorkflowExecutor › Execute with Return Strategy and Consistency › Execute Workflow with Return Strategies and Consistency Levels › Should execute complex workflow with SYNC + BLOCKING_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:700:17) at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:715:11)
Node.js v20 - integration v5 sdkdev (shard 1/3)
Failed test were found and 'fail-on-error' option is set to true
Node.js v20 - integration v5 sdkdev (shard 1/3)
Process completed with exit code 1.
ServiceRegistryClient › Should discover methods from a http service: src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to discover service methods for 'jsSdkTest-test_service_registry_discovery-1779464858137': Failed to read content from the Swagger URL: http://httpbin-server:8081/api-docs. Error: httpbin-server at handleSdkError (src/sdk/helpers/errors.ts:49:11) at ServiceRegistryClient.discover (src/sdk/clients/service-registry/ServiceRegistryClient.ts:347:21) at Object.<anonymous> (src/integration-tests/ServiceRegistryClient.test.ts:221:31)
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#L641
expect(received).toEqual(expected) // deep equality Expected: "BLOCKING_TASK_INPUT" Received: undefined at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:641:39)
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#L641
expect(received).toEqual(expected) // deep equality Expected: "BLOCKING_TASK" Received: undefined at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:641:39)
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#L620
thrown: "Exceeded timeout of 300000 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:620:13 at Array.forEach (<anonymous>) at src/integration-tests/WorkflowExecutor.test.ts:619:33 at src/integration-tests/WorkflowExecutor.test.ts:383:13 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#L620
thrown: "Exceeded timeout of 300000 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:620:13 at Array.forEach (<anonymous>) at src/integration-tests/WorkflowExecutor.test.ts:619:33 at src/integration-tests/WorkflowExecutor.test.ts:383:13 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#L641
expect(received).toEqual(expected) // deep equality Expected: "BLOCKING_TASK_INPUT" Received: undefined at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:641:39)
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#L641
expect(received).toEqual(expected) // deep equality Expected: "BLOCKING_TASK" Received: undefined at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:641:39)
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#L620
thrown: "Exceeded timeout of 300000 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:620:13 at Array.forEach (<anonymous>) at src/integration-tests/WorkflowExecutor.test.ts:619:33 at src/integration-tests/WorkflowExecutor.test.ts:383:13 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#L593
expect(received).toEqual(expected) // deep equality Expected: "TARGET_WORKFLOW" Received: undefined at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:593:46)
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.
ServiceRegistryClient › Should discover methods from a http service: src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to discover service methods for 'jsSdkTest-test_service_registry_discovery-1779464906616': Failed to read content from the Swagger URL: http://httpbin-server:8081/api-docs. Error: httpbin-server at handleSdkError (src/sdk/helpers/errors.ts:49:11) at ServiceRegistryClient.discover (src/sdk/clients/service-registry/ServiceRegistryClient.ts:347:21) at Object.<anonymous> (src/integration-tests/ServiceRegistryClient.test.ts:221:31)
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#L641
expect(received).toEqual(expected) // deep equality Expected: "BLOCKING_TASK_INPUT" Received: undefined at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:641:39)
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#L641
expect(received).toEqual(expected) // deep equality Expected: "BLOCKING_TASK" Received: undefined at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:641:39)
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#L620
thrown: "Exceeded timeout of 300000 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:620:13 at Array.forEach (<anonymous>) at src/integration-tests/WorkflowExecutor.test.ts:619:33 at src/integration-tests/WorkflowExecutor.test.ts:383:13 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#L620
thrown: "Exceeded timeout of 300000 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:620:13 at Array.forEach (<anonymous>) at src/integration-tests/WorkflowExecutor.test.ts:619:33 at src/integration-tests/WorkflowExecutor.test.ts:383:13 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#L641
expect(received).toEqual(expected) // deep equality Expected: "BLOCKING_TASK_INPUT" Received: undefined at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:641:39)
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#L641
expect(received).toEqual(expected) // deep equality Expected: "BLOCKING_TASK" Received: undefined at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:641:39)
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#L620
thrown: "Exceeded timeout of 300000 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:620:13 at Array.forEach (<anonymous>) at src/integration-tests/WorkflowExecutor.test.ts:619:33 at src/integration-tests/WorkflowExecutor.test.ts:383:13 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#L593
expect(received).toEqual(expected) // deep equality Expected: "TARGET_WORKFLOW" Received: undefined at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:593:46)
Node.js v22 - integration v5 sm (shard 1/3)
Failed test were found and 'fail-on-error' option is set to true
Node.js v22 - integration v5 sm (shard 1/3)
Process completed with exit code 1.
ServiceRegistryClient › Should discover methods from a http service: src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to discover service methods for 'jsSdkTest-test_service_registry_discovery-1779464941639': Failed to read content from the Swagger URL: http://httpbin-server:8081/api-docs. Error: httpbin-server at handleSdkError (src/sdk/helpers/errors.ts:49:11) at ServiceRegistryClient.discover (src/sdk/clients/service-registry/ServiceRegistryClient.ts:347:21) at Object.<anonymous> (src/integration-tests/ServiceRegistryClient.test.ts:221:31)
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#L641
expect(received).toEqual(expected) // deep equality Expected: "BLOCKING_TASK_INPUT" Received: undefined at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:641:39)
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#L641
expect(received).toEqual(expected) // deep equality Expected: "BLOCKING_TASK" Received: undefined at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:641:39)
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#L620
thrown: "Exceeded timeout of 300000 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:620:13 at Array.forEach (<anonymous>) at src/integration-tests/WorkflowExecutor.test.ts:619:33 at src/integration-tests/WorkflowExecutor.test.ts:383:13 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#L620
thrown: "Exceeded timeout of 300000 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:620:13 at Array.forEach (<anonymous>) at src/integration-tests/WorkflowExecutor.test.ts:619:33 at src/integration-tests/WorkflowExecutor.test.ts:383:13 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#L641
expect(received).toEqual(expected) // deep equality Expected: "BLOCKING_TASK_INPUT" Received: undefined at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:641:39)
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#L641
expect(received).toEqual(expected) // deep equality Expected: "BLOCKING_TASK" Received: undefined at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:641:39)
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#L620
thrown: "Exceeded timeout of 300000 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:620:13 at Array.forEach (<anonymous>) at src/integration-tests/WorkflowExecutor.test.ts:619:33 at src/integration-tests/WorkflowExecutor.test.ts:383:13 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#L593
expect(received).toEqual(expected) // deep equality Expected: "TARGET_WORKFLOW" Received: undefined at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:593:46)
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.
ServiceRegistryClient › Should discover methods from a http service: src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to discover service methods for 'jsSdkTest-test_service_registry_discovery-1779465164139': Failed to read content from the Swagger URL: http://httpbin-server:8081/api-docs. Error: httpbin-server at handleSdkError (src/sdk/helpers/errors.ts:49:11) at ServiceRegistryClient.discover (src/sdk/clients/service-registry/ServiceRegistryClient.ts:347:21) at Object.<anonymous> (src/integration-tests/ServiceRegistryClient.test.ts:221:31)
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#L641
expect(received).toEqual(expected) // deep equality Expected: "BLOCKING_TASK_INPUT" Received: undefined at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:641:39)
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#L641
expect(received).toEqual(expected) // deep equality Expected: "BLOCKING_TASK" Received: undefined at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:641:39)
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#L620
thrown: "Exceeded timeout of 300000 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:620:13 at Array.forEach (<anonymous>) at src/integration-tests/WorkflowExecutor.test.ts:619:33 at src/integration-tests/WorkflowExecutor.test.ts:383:13 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#L620
thrown: "Exceeded timeout of 300000 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:620:13 at Array.forEach (<anonymous>) at src/integration-tests/WorkflowExecutor.test.ts:619:33 at src/integration-tests/WorkflowExecutor.test.ts:383:13 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#L641
expect(received).toEqual(expected) // deep equality Expected: "BLOCKING_TASK_INPUT" Received: undefined at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:641:39)
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#L641
expect(received).toEqual(expected) // deep equality Expected: "BLOCKING_TASK" Received: undefined at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:641:39)
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#L620
thrown: "Exceeded timeout of 300000 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:620:13 at Array.forEach (<anonymous>) at src/integration-tests/WorkflowExecutor.test.ts:619:33 at src/integration-tests/WorkflowExecutor.test.ts:383:13 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#L593
expect(received).toEqual(expected) // deep equality Expected: "TARGET_WORKFLOW" Received: undefined at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:593:46)
Node.js v20 - integration v5 sm (shard 1/3)
The job has exceeded the maximum execution time of 25m0s
Node.js v20 - integration v5 sm (shard 1/3)
The operation was canceled.
ServiceRegistryClient › Should discover methods from a http service: src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to discover service methods for 'jsSdkTest-test_service_registry_discovery-1779464841166': Failed to read content from the Swagger URL: http://httpbin-server:8081/api-docs. Error: httpbin-server at handleSdkError (src/sdk/helpers/errors.ts:49:11) at ServiceRegistryClient.discover (src/sdk/clients/service-registry/ServiceRegistryClient.ts:347:21) at Object.<anonymous> (src/integration-tests/ServiceRegistryClient.test.ts:221:31)
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#L641
expect(received).toEqual(expected) // deep equality Expected: "BLOCKING_TASK_INPUT" Received: undefined at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:641:39)
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#L641
expect(received).toEqual(expected) // deep equality Expected: "BLOCKING_TASK" Received: undefined at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:641:39)
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#L620
thrown: "Exceeded timeout of 300000 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:620:13 at Array.forEach (<anonymous>) at src/integration-tests/WorkflowExecutor.test.ts:619:33 at src/integration-tests/WorkflowExecutor.test.ts:383:13 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#L620
thrown: "Exceeded timeout of 300000 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:620:13 at Array.forEach (<anonymous>) at src/integration-tests/WorkflowExecutor.test.ts:619:33 at src/integration-tests/WorkflowExecutor.test.ts:383:13 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#L641
expect(received).toEqual(expected) // deep equality Expected: "BLOCKING_TASK_INPUT" Received: undefined at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:641:39)
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#L641
expect(received).toEqual(expected) // deep equality Expected: "BLOCKING_TASK" Received: undefined at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:641:39)
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#L620
thrown: "Exceeded timeout of 300000 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:620:13 at Array.forEach (<anonymous>) at src/integration-tests/WorkflowExecutor.test.ts:619:33 at src/integration-tests/WorkflowExecutor.test.ts:383:13 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#L593
expect(received).toEqual(expected) // deep equality Expected: "TARGET_WORKFLOW" Received: undefined at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:593:46)
Node.js v24 - integration v5 sdkdev (shard 1/3)
The job has exceeded the maximum execution time of 25m0s
SDK Worker Registration › Worker execution (requires update-v2) › worker with concurrency processes multiple tasks: src/integration-tests/WorkerRegistration.test.ts#L241
expect(received).toBe(expected) // Object.is equality Expected: 3 Received: 6 at Object.<anonymous> (src/integration-tests/WorkerRegistration.test.ts:241:28)
SDK Worker Registration › Worker execution (requires update-v2) › TaskHandler auto-discovers and executes decorated workers: src/integration-tests/utils/waitForWorkflowStatus.ts#L44
Workflow did not reach status COMPLETED within 60000ms at waitForWorkflowStatus (src/integration-tests/utils/waitForWorkflowStatus.ts:44:9) at Object.<anonymous> (src/integration-tests/WorkerRegistration.test.ts:139:28)
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#L641
expect(received).toEqual(expected) // deep equality Expected: "BLOCKING_TASK_INPUT" Received: undefined at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:641:39)
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#L641
expect(received).toEqual(expected) // deep equality Expected: "BLOCKING_TASK" Received: undefined at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:641:39)
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#L620
thrown: "Exceeded timeout of 300000 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:620:13 at Array.forEach (<anonymous>) at src/integration-tests/WorkflowExecutor.test.ts:619:33 at src/integration-tests/WorkflowExecutor.test.ts:383:13 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#L620
thrown: "Exceeded timeout of 300000 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:620:13 at Array.forEach (<anonymous>) at src/integration-tests/WorkflowExecutor.test.ts:619:33 at src/integration-tests/WorkflowExecutor.test.ts:383:13 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#L641
expect(received).toEqual(expected) // deep equality Expected: "BLOCKING_TASK_INPUT" Received: undefined at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:641:39)
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#L641
expect(received).toEqual(expected) // deep equality Expected: "BLOCKING_TASK" Received: undefined at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:641:39)
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#L620
thrown: "Exceeded timeout of 300000 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:620:13 at Array.forEach (<anonymous>) at src/integration-tests/WorkflowExecutor.test.ts:619:33 at src/integration-tests/WorkflowExecutor.test.ts:383:13 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#L593
expect(received).toEqual(expected) // deep equality Expected: "TARGET_WORKFLOW" Received: undefined at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:593:46)
Node.js v24 - 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 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 (shard 3/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 3/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 sm (shard 3/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 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 v20 - integration v5 sm (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 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 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 v22 - integration v5 sm (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 v22 - integration v5 sm (shard 3/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/
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 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 v24 - integration v5 sm (shard 3/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 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. 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 sm (shard 1/3)
Codecov: Failed to properly upload report: The process '/home/runner/work/_actions/codecov/codecov-action/v4/dist/codecov' failed with exit code 1
Node.js v24 - 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. 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 sdkdev (shard 1/3)
Codecov: Failed to properly upload report: The process '/home/runner/work/_actions/codecov/codecov-action/v4/dist/codecov' failed with exit code 1