test oidc trusted publishing #564
Annotations
93 errors and 22 warnings
|
Node.js v20 - integration v4 (shard 1/3)
Failed test were found and 'fail-on-error' option is set to true
|
|
Node.js v20 - integration v4 (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#L214
expect(received).toEqual(expected) // deep equality
Expected: "IN_PROGRESS"
Received: "FAILED_WITH_TERMINAL_ERROR"
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:214:24)
|
|
Node.js v20 - integration v5 (shard 2/3)
Failed test were found and 'fail-on-error' option is set to true
|
|
Node.js v20 - integration v5 (shard 2/3)
Process completed with exit code 1.
|
|
WorkflowExecutor Complete Coverage › Error Paths › goBackToTask should throw when no matching task found:
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:111:21)
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:799:20)
|
|
WorkflowExecutor Complete Coverage › Signal Async › signalAsync should signal a workflow asynchronously:
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:111:21)
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:715:20)
|
|
WorkflowExecutor Complete Coverage › GoBack Methods › goBackToFirstTaskMatchingType should rerun from a task type:
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:111:21)
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:696:20)
|
|
WorkflowExecutor Complete Coverage › GoBack Methods › goBackToTask should rerun from a matching task:
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:111:21)
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:664:20)
|
|
WorkflowExecutor Complete Coverage › Update State › updateState should update workflow and task state:
src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to update state for workflow 'a4647c2f-73f0-11f1-80c1-8e8815462681'
at handleSdkError (src/sdk/helpers/errors.ts:49:11)
at WorkflowExecutor.updateState (src/sdk/clients/workflow/WorkflowExecutor.ts:814:21)
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:641:22)
|
|
Node.js v20 - integration v5 (shard 1/3)
Failed test were found and 'fail-on-error' option is set to true
|
|
ServiceRegistryClient › Should discover methods from a gRPC service:
src/integration-tests/ServiceRegistryClient.test.ts#L21
thrown: "Exceeded timeout of 60000 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/ServiceRegistryClient.test.ts:21:12
at Object.<anonymous> (src/integration-tests/ServiceRegistryClient.test.ts:15:19)
|
|
ServiceRegistryClient › Should discover methods from a http service:
src/integration-tests/ServiceRegistryClient.test.ts#L21
thrown: "Exceeded timeout of 60000 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/ServiceRegistryClient.test.ts:21:12
at Object.<anonymous> (src/integration-tests/ServiceRegistryClient.test.ts:15:19)
|
|
ServiceRegistryClient › Should add a service method to a registry:
src/integration-tests/ServiceRegistryClient.test.ts#L21
thrown: "Exceeded timeout of 60000 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/ServiceRegistryClient.test.ts:21:12
at Object.<anonymous> (src/integration-tests/ServiceRegistryClient.test.ts:15:19)
|
|
ServiceRegistryClient › Should add and remove a service registry:
src/integration-tests/ServiceRegistryClient.test.ts#L21
thrown: "Exceeded timeout of 60000 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/ServiceRegistryClient.test.ts:21:12
at Object.<anonymous> (src/integration-tests/ServiceRegistryClient.test.ts:15:19)
|
|
ServiceRegistryClient › Should add and retrieve a service registry:
src/integration-tests/ServiceRegistryClient.test.ts#L21
thrown: "Exceeded timeout of 60000 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/ServiceRegistryClient.test.ts:21:12
at Object.<anonymous> (src/integration-tests/ServiceRegistryClient.test.ts:15:19)
|
|
SDK Worker Registration › update-v2 endpoint verification › SDK detects and uses /api/tasks/update-v2 on v5 server:
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/WorkerRegistration.test.ts:693:7)
|
|
SDK Worker Registration › Worker execution (requires update-v2) › multiple workers can be registered and executed:
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/WorkerRegistration.test.ts:488:5)
|
|
SDK Worker Registration › Worker execution (requires update-v2) › event listeners receive lifecycle events:
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/WorkerRegistration.test.ts:407:5)
|
|
SDK Worker Registration › Worker execution (requires update-v2) › NonRetryableException marks task as terminal failure:
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/WorkerRegistration.test.ts:315:5)
|
|
SDK Worker Registration › Worker execution (requires update-v2) › worker with concurrency processes multiple tasks:
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:171:21)
at executeWorkflowWithRetry (src/integration-tests/utils/executeWorkflowWithRetry.ts:31:14)
at Object.<anonymous> (src/integration-tests/WorkerRegistration.test.ts:218:28)
|
|
Node.js v22 - integration v5 (shard 1/3)
Failed test were found and 'fail-on-error' option is set to true
|
|
SchemaClient › Schema Deletion › deleteSchemaByName should remove all versions:
src/integration-tests/SchemaClient.test.ts#L34
thrown: "Exceeded timeout of 60000 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/SchemaClient.test.ts:34:12
at Object.<anonymous> (src/integration-tests/SchemaClient.test.ts:16:19)
|
|
SchemaClient › Schema Deletion › deleteSchema should remove a specific version:
src/integration-tests/SchemaClient.test.ts#L34
thrown: "Exceeded timeout of 60000 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/SchemaClient.test.ts:34:12
at Object.<anonymous> (src/integration-tests/SchemaClient.test.ts:16:19)
|
|
SchemaClient › Schema CRUD › getSchema version 2 should return the updated schema:
src/integration-tests/SchemaClient.test.ts#L34
thrown: "Exceeded timeout of 60000 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/SchemaClient.test.ts:34:12
at Object.<anonymous> (src/integration-tests/SchemaClient.test.ts:16:19)
|
|
SchemaClient › Schema CRUD › registerSchema with newVersion should create version 2:
src/integration-tests/SchemaClient.test.ts#L34
thrown: "Exceeded timeout of 60000 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/SchemaClient.test.ts:34:12
at Object.<anonymous> (src/integration-tests/SchemaClient.test.ts:16:19)
|
|
SchemaClient › Schema CRUD › getAllSchemas should include the test schema:
src/integration-tests/SchemaClient.test.ts#L34
thrown: "Exceeded timeout of 60000 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/SchemaClient.test.ts:34:12
at Object.<anonymous> (src/integration-tests/SchemaClient.test.ts:16:19)
|
|
SchemaClient › Schema CRUD › getSchemaByName should return latest version:
src/integration-tests/SchemaClient.test.ts#L34
thrown: "Exceeded timeout of 60000 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/SchemaClient.test.ts:34:12
at Object.<anonymous> (src/integration-tests/SchemaClient.test.ts:16:19)
|
|
SchemaClient › Schema CRUD › getSchema should return schema by name and version:
src/integration-tests/SchemaClient.test.ts#L34
thrown: "Exceeded timeout of 60000 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/SchemaClient.test.ts:34:12
at Object.<anonymous> (src/integration-tests/SchemaClient.test.ts:16:19)
|
|
SchemaClient › Schema CRUD › registerSchema should create a new schema:
src/integration-tests/SchemaClient.test.ts#L34
thrown: "Exceeded timeout of 60000 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/SchemaClient.test.ts:34:12
at Object.<anonymous> (src/integration-tests/SchemaClient.test.ts:16:19)
|
|
E2E: 5-task workflow × 50 executions › 50 workflows with 5 sequential tasks each all complete with correct output:
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:111:21)
at Object.<anonymous> (src/integration-tests/E2EFiveTaskWorkflow.test.ts:113:20)
|
|
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:171:21)
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:624:26)
|
|
Node.js v20 - integration v5 (shard 3/3)
Failed test were found and 'fail-on-error' option is set to true
|
|
SecretClient › SecretClient V4+ › Secret CRUD › listSecretsThatUserCanGrantAccessTo should return an array:
src/integration-tests/SecretClient.test.ts#L28
thrown: "Exceeded timeout of 60000 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/SecretClient.test.ts:28:12
at src/integration-tests/SecretClient.test.ts:16:21
at Object.<anonymous> (src/integration-tests/SecretClient.test.ts:15:9)
|
|
SecretClient › SecretClient V4+ › Secret CRUD › listAllSecretNames should include the test secret:
src/integration-tests/SecretClient.test.ts#L28
thrown: "Exceeded timeout of 60000 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/SecretClient.test.ts:28:12
at src/integration-tests/SecretClient.test.ts:16:21
at Object.<anonymous> (src/integration-tests/SecretClient.test.ts:15:9)
|
|
SecretClient › SecretClient V4+ › Secret CRUD › putSecret should update an existing secret:
src/integration-tests/SecretClient.test.ts#L28
thrown: "Exceeded timeout of 60000 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/SecretClient.test.ts:28:12
at src/integration-tests/SecretClient.test.ts:16:21
at Object.<anonymous> (src/integration-tests/SecretClient.test.ts:15:9)
|
|
SecretClient › SecretClient V4+ › Secret CRUD › getSecret should return the stored value:
src/integration-tests/SecretClient.test.ts#L28
thrown: "Exceeded timeout of 60000 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/SecretClient.test.ts:28:12
at src/integration-tests/SecretClient.test.ts:16:21
at Object.<anonymous> (src/integration-tests/SecretClient.test.ts:15:9)
|
|
SecretClient › SecretClient V4+ › Secret CRUD › secretExists should return true for existing secret:
src/integration-tests/SecretClient.test.ts#L28
thrown: "Exceeded timeout of 60000 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/SecretClient.test.ts:28:12
at src/integration-tests/SecretClient.test.ts:16:21
at Object.<anonymous> (src/integration-tests/SecretClient.test.ts:15:9)
|
|
SecretClient › SecretClient V4+ › Secret CRUD › putSecret should store a new secret:
src/integration-tests/SecretClient.test.ts#L28
thrown: "Exceeded timeout of 60000 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/SecretClient.test.ts:28:12
at src/integration-tests/SecretClient.test.ts:16:21
at Object.<anonymous> (src/integration-tests/SecretClient.test.ts:15:9)
|
|
SchedulerClient › SchedulerClient V4+ › Should be able to retrieve next (default 3) execution times for a scheduler:
src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to get next few schedules
at handleSdkError (src/sdk/helpers/errors.ts:49:11)
at SchedulerClient.getNextFewSchedules (src/sdk/clients/scheduler/SchedulerClient.ts:183:21)
at Object.<anonymous> (src/integration-tests/SchedulerClient.test.ts:167:20)
|
|
SchedulerClient › SchedulerClient V4+ › Should be able to delete the schedule:
src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to delete schedule 'jsSdkTestSchedule_1782761510244'
at handleSdkError (src/sdk/helpers/errors.ts:49:11)
at SchedulerClient.deleteSchedule (src/sdk/clients/scheduler/SchedulerClient.ts:134:21)
at Object.<anonymous> (src/integration-tests/SchedulerClient.test.ts:150:5)
|
|
SchedulerClient › SchedulerClient V4+ › Should be able to pause the schedule:
src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to pause schedule 'jsSdkTestSchedule_1782761510244'
at handleSdkError (src/sdk/helpers/errors.ts:49:11)
at SchedulerClient.pauseSchedule (src/sdk/clients/scheduler/SchedulerClient.ts:98:21)
at Object.<anonymous> (src/integration-tests/SchedulerClient.test.ts:138:5)
|
|
SchedulerClient › SchedulerClient V4+ › Should be able to see the result in executed schedule:
src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to search schedules
at handleSdkError (src/sdk/helpers/errors.ts:49:11)
at SchedulerClient.search (src/sdk/clients/scheduler/SchedulerClient.ts:62:21)
at Object.<anonymous> (src/integration-tests/SchedulerClient.test.ts:125:20)
|
|
Node.js v22 - integration v5 (shard 3/3)
Failed test were found and 'fail-on-error' option is set to true
|
|
Node.js v22 - integration v5 (shard 3/3)
Process completed with exit code 1.
|
|
TaskManager › TaskManager workflow execution › Should run workflow with worker:
src/integration-tests/utils/waitForWorkflowCompletion.ts#L43
Workflow 8407eb44-73f1-11f1-b276-564c899bcb5b did not complete within 30000ms
at waitForWorkflowCompletion (src/integration-tests/utils/waitForWorkflowCompletion.ts:43:9)
at Object.<anonymous> (src/integration-tests/TaskManager.test.ts:135:28)
|
|
Node.js v22 - 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/integration-tests/WorkflowExecutor.complete.test.ts#L63
thrown: "Exceeded timeout of 120000 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.complete.test.ts:63:12
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:42:9)
|
|
WorkflowExecutor Complete Coverage › Correlation IDs › getByCorrelationIds should return workflows by correlation:
src/integration-tests/WorkflowExecutor.complete.test.ts#L63
thrown: "Exceeded timeout of 120000 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.complete.test.ts:63:12
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:42:9)
|
|
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-1782761607771, version: 1
at handleSdkError (src/sdk/helpers/errors.ts:49:11)
at WorkflowExecutor.startWorkflow (src/sdk/clients/workflow/WorkflowExecutor.ts:111:21)
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:208:20)
|
|
WorkflowExecutor Complete Coverage › Execution Info › search should find the workflow:
src/integration-tests/WorkflowExecutor.complete.test.ts#L63
thrown: "Exceeded timeout of 120000 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.complete.test.ts:63:12
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:42:9)
|
|
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-1782761607771, version: 1
at handleSdkError (src/sdk/helpers/errors.ts:49:11)
at WorkflowExecutor.startWorkflow (src/sdk/clients/workflow/WorkflowExecutor.ts:111:21)
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:208:20)
|
|
WorkflowExecutor Complete Coverage › Execution Info › getWorkflowStatus (V4+) › getWorkflowStatus should return status summary:
src/integration-tests/WorkflowExecutor.complete.test.ts#L63
thrown: "Exceeded timeout of 120000 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.complete.test.ts:63:12
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:42:9)
|
|
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-1782761607771, version: 1
at handleSdkError (src/sdk/helpers/errors.ts:49:11)
at WorkflowExecutor.startWorkflow (src/sdk/clients/workflow/WorkflowExecutor.ts:111:21)
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:208:20)
|
|
WorkflowExecutor Complete Coverage › Execution Info › getExecution should return full workflow with tasks:
src/integration-tests/WorkflowExecutor.complete.test.ts#L63
thrown: "Exceeded timeout of 120000 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.complete.test.ts:63:12
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:42:9)
|
|
WorkflowExecutor Complete Coverage › Start Methods › startWorkflowByName should start a workflow with direct params:
src/integration-tests/WorkflowExecutor.complete.test.ts#L63
thrown: "Exceeded timeout of 120000 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.complete.test.ts:63:12
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:42:9)
|
|
WorkflowExecutor Complete Coverage › Start Methods › startWorkflows should start multiple workflows in batch:
src/integration-tests/WorkflowExecutor.complete.test.ts#L63
thrown: "Exceeded timeout of 120000 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.complete.test.ts:63:12
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:42:9)
|
|
Node.js v24 - integration v4 (shard 1/3)
Failed test were found and 'fail-on-error' option is set to true
|
|
Node.js v24 - integration v4 (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#L214
expect(received).toEqual(expected) // deep equality
Expected: "IN_PROGRESS"
Received: "FAILED_WITH_TERMINAL_ERROR"
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:214:24)
|
|
Node.js v24 - integration v5 (shard 2/3)
Failed test were found and 'fail-on-error' option is set to true
|
|
PromptClient › Prompt Testing › testPrompt should attempt to test the prompt against an LLM:
src/integration-tests/PromptClient.test.ts#L31
thrown: "Exceeded timeout of 60000 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/PromptClient.test.ts:31:12
at Object.<anonymous> (src/integration-tests/PromptClient.test.ts:16:19)
|
|
PromptClient › Prompt Tags › deletePromptTags should remove specific tags:
src/integration-tests/PromptClient.test.ts#L31
thrown: "Exceeded timeout of 60000 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/PromptClient.test.ts:31:12
at Object.<anonymous> (src/integration-tests/PromptClient.test.ts:16:19)
|
|
PromptClient › Prompt Tags › getPromptTags should return the set tags:
src/integration-tests/PromptClient.test.ts#L31
thrown: "Exceeded timeout of 60000 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/PromptClient.test.ts:31:12
at Object.<anonymous> (src/integration-tests/PromptClient.test.ts:16:19)
|
|
PromptClient › Prompt Tags › setPromptTags should set tags on the prompt:
src/integration-tests/PromptClient.test.ts#L31
thrown: "Exceeded timeout of 60000 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/PromptClient.test.ts:31:12
at Object.<anonymous> (src/integration-tests/PromptClient.test.ts:16:19)
|
|
PromptClient › Prompt CRUD › savePrompt with models should accept model list:
src/integration-tests/PromptClient.test.ts#L31
thrown: "Exceeded timeout of 60000 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/PromptClient.test.ts:31:12
at Object.<anonymous> (src/integration-tests/PromptClient.test.ts:16:19)
|
|
PromptClient › Prompt CRUD › updatePrompt should modify the prompt template:
src/integration-tests/PromptClient.test.ts#L31
thrown: "Exceeded timeout of 60000 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/PromptClient.test.ts:31:12
at Object.<anonymous> (src/integration-tests/PromptClient.test.ts:16:19)
|
|
PromptClient › Prompt CRUD › getPrompts should include the created prompt:
src/integration-tests/PromptClient.test.ts#L31
thrown: "Exceeded timeout of 60000 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/PromptClient.test.ts:31:12
at Object.<anonymous> (src/integration-tests/PromptClient.test.ts:16:19)
|
|
PromptClient › Prompt CRUD › getPrompt should return the created prompt:
src/integration-tests/PromptClient.test.ts#L31
thrown: "Exceeded timeout of 60000 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/PromptClient.test.ts:31:12
at Object.<anonymous> (src/integration-tests/PromptClient.test.ts:16:19)
|
|
PromptClient › Prompt CRUD › savePrompt should create a new prompt template:
src/integration-tests/PromptClient.test.ts#L31
thrown: "Exceeded timeout of 60000 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/PromptClient.test.ts:31:12
at Object.<anonymous> (src/integration-tests/PromptClient.test.ts:16:19)
|
|
Lease Extension — end-to-end validation › WITH lease extension: heartbeat fires before responseTimeout:
src/integration-tests/LeaseExtension.validation.test.ts#L170
thrown: "<html>
<head><title>503 Service Temporarily Unavailable</title></head>
<body>
<center><h1>503 Service Temporarily Unavailable</h1></center>
<hr><center>nginx</center>
</body>
</html>
"
at src/integration-tests/LeaseExtension.validation.test.ts:170:7
at Object.<anonymous> (src/integration-tests/LeaseExtension.validation.test.ts:52:9)
|
|
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 multiple log entries:
src/integration-tests/TaskClient.complete.test.ts#L43
thrown: "Exceeded timeout of 60000 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/TaskClient.complete.test.ts:43:12
at Object.<anonymous> (src/integration-tests/TaskClient.complete.test.ts:29:9)
|
|
TaskClient Complete Coverage › Task Logs › addTaskLog should add a log entry to a task:
src/integration-tests/TaskClient.complete.test.ts#L43
thrown: "Exceeded timeout of 60000 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/TaskClient.complete.test.ts:43:12
at Object.<anonymous> (src/integration-tests/TaskClient.complete.test.ts:29:9)
|
|
TaskClient Complete Coverage › Task Queries › getTaskPollData should return poll data:
src/integration-tests/TaskClient.complete.test.ts#L43
thrown: "Exceeded timeout of 60000 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/TaskClient.complete.test.ts:43:12
at Object.<anonymous> (src/integration-tests/TaskClient.complete.test.ts:29:9)
|
|
TaskClient Complete Coverage › Task Queries › getQueueSizeForTask should return queue sizes:
src/integration-tests/TaskClient.complete.test.ts#L43
thrown: "Exceeded timeout of 60000 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/TaskClient.complete.test.ts:43:12
at Object.<anonymous> (src/integration-tests/TaskClient.complete.test.ts:29:9)
|
|
TaskClient Complete Coverage › Task Queries › search (V4+) › search should find tasks:
src/integration-tests/TaskClient.complete.test.ts#L43
thrown: "Exceeded timeout of 60000 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/TaskClient.complete.test.ts:43:12
at Object.<anonymous> (src/integration-tests/TaskClient.complete.test.ts:29:9)
|
|
TaskClient Complete Coverage › Task Queries › getTask should return task details by ID:
src/integration-tests/TaskClient.complete.test.ts#L43
thrown: "Exceeded timeout of 60000 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/TaskClient.complete.test.ts:43:12
at Object.<anonymous> (src/integration-tests/TaskClient.complete.test.ts:29:9)
|
|
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 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:171:9)
|
|
Node.js v24 - integration v5 (shard 1/3)
Failed test were found and 'fail-on-error' option is set to true
|
|
TaskManager › worker example:
src/integration-tests/readme.test.ts#L29
thrown: "Exceeded timeout of 120000 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/readme.test.ts:29:7
at Object.<anonymous> (src/integration-tests/readme.test.ts:13:9)
|
|
ServiceRegistryClient › Should discover methods from a gRPC service:
src/integration-tests/ServiceRegistryClient.test.ts#L21
thrown: "Exceeded timeout of 60000 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/ServiceRegistryClient.test.ts:21:12
at Object.<anonymous> (src/integration-tests/ServiceRegistryClient.test.ts:15:19)
|
|
ServiceRegistryClient › Should discover methods from a http service:
src/integration-tests/ServiceRegistryClient.test.ts#L21
thrown: "Exceeded timeout of 60000 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/ServiceRegistryClient.test.ts:21:12
at Object.<anonymous> (src/integration-tests/ServiceRegistryClient.test.ts:15:19)
|
|
ServiceRegistryClient › Should add a service method to a registry:
src/integration-tests/ServiceRegistryClient.test.ts#L21
thrown: "Exceeded timeout of 60000 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/ServiceRegistryClient.test.ts:21:12
at Object.<anonymous> (src/integration-tests/ServiceRegistryClient.test.ts:15:19)
|
|
ServiceRegistryClient › Should add and remove a service registry:
src/integration-tests/ServiceRegistryClient.test.ts#L21
thrown: "Exceeded timeout of 60000 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/ServiceRegistryClient.test.ts:21:12
at Object.<anonymous> (src/integration-tests/ServiceRegistryClient.test.ts:15:19)
|
|
ServiceRegistryClient › Should add and retrieve a service registry:
src/integration-tests/ServiceRegistryClient.test.ts#L21
thrown: "Exceeded timeout of 60000 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/ServiceRegistryClient.test.ts:21:12
at Object.<anonymous> (src/integration-tests/ServiceRegistryClient.test.ts:15:19)
|
|
SDK Worker Registration › update-v2 endpoint verification › SDK detects and uses /api/tasks/update-v2 on v5 server:
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/WorkerRegistration.test.ts:693:7)
|
|
SDK Worker Registration › Worker execution (requires update-v2) › multiple workers can be registered and executed:
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/WorkerRegistration.test.ts:488:5)
|
|
SDK Worker Registration › Worker execution (requires update-v2) › event listeners receive lifecycle events:
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/WorkerRegistration.test.ts:407:5)
|
|
SDK Worker Registration › Worker execution (requires update-v2) › NonRetryableException marks task as terminal failure:
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/WorkerRegistration.test.ts:315:5)
|
|
linter
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Node.js v24 - unit tests
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Node.js v22 - unit tests
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Node.js v20 - unit tests
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Node.js v20 - integration v4 (shard 1/3)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Node.js v20 - integration v4 (shard 2/3)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. 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 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. 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 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Node.js v20 - integration v4 (shard 3/3)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. 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 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. 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 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. 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 3/3)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. 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 2/3)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. 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 3/3)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. 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 3/3)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. 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 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. 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 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. 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 2/3)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. 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 3/3)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. 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 2/3)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. 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 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. 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 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|