Certification worker metrics #519
chrishagglund-ship-itAnnotations
15 errors and 5 warnings
|
Node.js v20 - integration v5 (shard 2/3)
Failed test were found and 'fail-on-error' option is set to true
|
|
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:83:21)
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:797: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:83:21)
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:713: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:83:21)
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:694: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:83:21)
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:662:20)
|
|
WorkflowExecutor Complete Coverage › Update State › updateState should update workflow and task state:
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:83:21)
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:625:20)
|
|
WorkflowExecutor Complete Coverage › Update Variables › updateVariables should update workflow variables:
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:83:21)
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:601:20)
|
|
WorkflowExecutor Complete Coverage › Test Workflow › testWorkflow should simulate a workflow execution:
src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to get workflow definition 'jsSdkTest-taskWf-1776697887158'
at handleSdkError (src/sdk/helpers/errors.ts:49:11)
at MetadataClient.getWorkflowDef (src/sdk/clients/metadata/MetadataClient.ts:153:21)
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:576:21)
|
|
WorkflowExecutor Complete Coverage › Delete Workflow › deleteWorkflow should remove a completed workflow execution:
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:83:21)
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:560:20)
|
|
WorkflowExecutor Complete Coverage › Skip Task › skipTasksFromWorkflow should skip a scheduled 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:83:21)
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:516:20)
|
|
WorkflowExecutor Complete Coverage › Rerun › reRun should re-execute a completed workflow from a task:
src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to update task by reference name
at handleSdkError (src/sdk/helpers/errors.ts:49:11)
at WorkflowExecutor.updateTaskByRefName (src/sdk/clients/workflow/WorkflowExecutor.ts:552:21)
at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:493:7)
|
|
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.
|
|
E2E: 5-task workflow × 50 executions › 50 workflows with 5 sequential tasks each all complete with correct output:
src/integration-tests/E2EFiveTaskWorkflow.test.ts#L161
expect(received).toBe(expected) // Object.is equality
Expected: 50
Received: 52
at Object.<anonymous> (src/integration-tests/E2EFiveTaskWorkflow.test.ts:161:43)
|
|
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 execute workflow
at handleSdkError (src/sdk/helpers/errors.ts:49:11)
at WorkflowExecutor.executeWorkflow (src/sdk/clients/workflow/WorkflowExecutor.ts:143:21)
at executeWorkflowWithRetry (src/integration-tests/utils/executeWorkflowWithRetry.ts:31:14)
at Object.<anonymous> (src/integration-tests/WorkerRegistration.test.ts:504:28)
|
|
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 v20 - integration v5 (shard 2/3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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 v20 - 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 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/
|