chore(deps): bump picomatch #146
ci.yml
on: push
unit-tests
1m 29s
local_integration_8_8
3m 22s
local_integration_8_8_against_8_9
3m 34s
saas_integration_8_8
0s
saas_integration
0s
local_integration
0s
local_multitenancy_integration
0s
Annotations
3 errors and 3 warnings
|
local_integration_8_8_against_8_9
Process completed with exit code 1.
|
|
src/__tests__/zeebe/integration/Worker-onReady.spec.ts > Does not emit the ready event if there is no broker:
src/__tests__/zeebe/integration/Worker-onReady.spec.ts#L92
Error: Test timed out in 40000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ src/__tests__/zeebe/integration/Worker-onReady.spec.ts:92:79
|
|
Unhandled error:
src/__tests__/zeebe/integration/Worker-onReady.spec.ts#L111
AssertionError: expected 1 to be +0 // Object.is equality
❯ Timeout._onTimeout src/__tests__/zeebe/integration/Worker-onReady.spec.ts:111:20
This error originated in "src/__tests__/zeebe/integration/Worker-onReady.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The latest test that might've caused the error is "Does not emit the ready event if there is no broker". It might mean one of the following:
- The error was thrown, while Vitest was running this test.
- If the error occurred after the test had been completed, this was the last documented test before it was thrown.
|
|
unit-tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@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/
|
|
local_integration_8_8
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
local_integration_8_8_against_8_9
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|