Skip to content

Features - v3

Features - v3 #482

Triggered via pull request March 10, 2026 01:06
Status Failure
Total duration 9m 13s
Artifacts

pull_request.yml

on: pull_request
linter
14s
linter
Node.js 22 - integration tests (v5)
9m 10s
Node.js 22 - integration tests (v5)
Matrix: unit-tests
Fit to window
Zoom out
Zoom in

Annotations

6 errors
Node.js 22 - integration tests (v5)
Failed test were found and 'fail-on-error' option is set to true
Node.js 22 - integration tests (v5)
Process completed with exit code 1.
E2E: 5-task workflow × 50 executions › 50 workflows with 5 sequential tasks each all complete with correct output: src/integration-tests/utils/waitForWorkflowStatus.ts#L44
Workflow did not reach status COMPLETED within 300000ms at waitForWorkflowStatus (src/integration-tests/utils/waitForWorkflowStatus.ts:44:9) at async Promise.all (index 34) at Object.<anonymous> (src/integration-tests/E2EFiveTaskWorkflow.test.ts:115:23)
WorkflowExecutor › Should return workflow status detail: src/integration-tests/WorkflowExecutor.test.ts#L138
expect(received).toBeDefined() Received: undefined at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:138:25)
WorkflowExecutor › Should be able to get workflow execution status: src/integration-tests/WorkflowExecutor.test.ts#L123
expect(received).toBeDefined() Received: undefined at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:123:25)
WorkflowExecutor › Should be able to start a workflow: src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to start workflow: Response body object should not be disturbed or locked at handleSdkError (src/sdk/helpers/errors.ts:49:11) at WorkflowExecutor.startWorkflow (src/sdk/clients/workflow/WorkflowExecutor.ts:83:21) at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:101:19)