Process completed with exit code 1.

BrowserLaunchError: Failed to launch browser. Please check the following: - Try installing a browser, if it's missing, by running `npx @puppeteer/browsers install chromium --path [path]` and pointing `executablePath` to the downloaded executable (https://pptr.dev/browsers-api) The original error is available in the `cause` property. Below is the error received when trying to launch a browser: ​ ❯ PuppeteerPlugin._throwAugmentedLaunchError node_modules/@crawlee/src/abstract-classes/browser-plugin.ts:261:14 ❯ PuppeteerPlugin._launch node_modules/@crawlee/src/puppeteer/puppeteer-plugin.ts:88:21 ❯ Browser.start test/_helper.ts:13:24 ❯ test/runs.test.ts:19:9 Caused by: Caused by: Error: Could not find Chrome (ver. 146.0.7680.153). This can occur if either 1. you did not perform an installation before running the script (e.g. `npx puppeteer browsers install chrome`) or 2. your cache path is incorrectly configured (which is: /home/runner/.cache/puppeteer). For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration. ❯ ChromeLauncher.resolveExecutablePath node_modules/puppeteer-core/lib/cjs/puppeteer/node/BrowserLauncher.js:334:27 ❯ ChromeLauncher.computeLaunchArguments node_modules/puppeteer-core/lib/cjs/puppeteer/node/ChromeLauncher.js:94:24 ❯ ChromeLauncher.launch node_modules/puppeteer-core/lib/cjs/puppeteer/node/BrowserLauncher.js:85:28 ❯ PuppeteerPlugin._launch node_modules/@crawlee/browser-pool/puppeteer/puppeteer-plugin.js:52:27 ❯ Browser.start test/_helper.ts:13:24 ❯ test/runs.test.ts:19:9

BrowserLaunchError: Failed to launch browser. Please check the following: - Try installing a browser, if it's missing, by running `npx @puppeteer/browsers install chromium --path [path]` and pointing `executablePath` to the downloaded executable (https://pptr.dev/browsers-api) The original error is available in the `cause` property. Below is the error received when trying to launch a browser: ​ ❯ PuppeteerPlugin._throwAugmentedLaunchError node_modules/@crawlee/src/abstract-classes/browser-plugin.ts:261:14 ❯ PuppeteerPlugin._launch node_modules/@crawlee/src/puppeteer/puppeteer-plugin.ts:88:21 ❯ Browser.start test/_helper.ts:13:24 ❯ test/request_queues.test.ts:20:9 Caused by: Caused by: Error: Could not find Chrome (ver. 146.0.7680.153). This can occur if either 1. you did not perform an installation before running the script (e.g. `npx puppeteer browsers install chrome`) or 2. your cache path is incorrectly configured (which is: /home/runner/.cache/puppeteer). For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration. ❯ ChromeLauncher.resolveExecutablePath node_modules/puppeteer-core/lib/cjs/puppeteer/node/BrowserLauncher.js:334:27 ❯ ChromeLauncher.computeLaunchArguments node_modules/puppeteer-core/lib/cjs/puppeteer/node/ChromeLauncher.js:94:24 ❯ ChromeLauncher.launch node_modules/puppeteer-core/lib/cjs/puppeteer/node/BrowserLauncher.js:85:28 ❯ PuppeteerPlugin._launch node_modules/@crawlee/browser-pool/puppeteer/puppeteer-plugin.js:52:27 ❯ Browser.start test/_helper.ts:13:24 ❯ test/request_queues.test.ts:20:9

BrowserLaunchError: Failed to launch browser. Please check the following: - Try installing a browser, if it's missing, by running `npx @puppeteer/browsers install chromium --path [path]` and pointing `executablePath` to the downloaded executable (https://pptr.dev/browsers-api) The original error is available in the `cause` property. Below is the error received when trying to launch a browser: ​ ❯ PuppeteerPlugin._throwAugmentedLaunchError node_modules/@crawlee/src/abstract-classes/browser-plugin.ts:261:14 ❯ PuppeteerPlugin._launch node_modules/@crawlee/src/puppeteer/puppeteer-plugin.ts:88:21 ❯ Browser.start test/_helper.ts:13:24 ❯ test/logs.test.ts:16:9 Caused by: Caused by: Error: Could not find Chrome (ver. 146.0.7680.153). This can occur if either 1. you did not perform an installation before running the script (e.g. `npx puppeteer browsers install chrome`) or 2. your cache path is incorrectly configured (which is: /home/runner/.cache/puppeteer). For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration. ❯ ChromeLauncher.resolveExecutablePath node_modules/puppeteer-core/lib/cjs/puppeteer/node/BrowserLauncher.js:334:27 ❯ ChromeLauncher.computeLaunchArguments node_modules/puppeteer-core/lib/cjs/puppeteer/node/ChromeLauncher.js:94:24 ❯ ChromeLauncher.launch node_modules/puppeteer-core/lib/cjs/puppeteer/node/BrowserLauncher.js:85:28 ❯ PuppeteerPlugin._launch node_modules/@crawlee/browser-pool/puppeteer/puppeteer-plugin.js:52:27 ❯ Browser.start test/_helper.ts:13:24 ❯ test/logs.test.ts:16:9

BrowserLaunchError: Failed to launch browser. Please check the following: - Try installing a browser, if it's missing, by running `npx @puppeteer/browsers install chromium --path [path]` and pointing `executablePath` to the downloaded executable (https://pptr.dev/browsers-api) The original error is available in the `cause` property. Below is the error received when trying to launch a browser: ​ ❯ PuppeteerPlugin._throwAugmentedLaunchError node_modules/@crawlee/src/abstract-classes/browser-plugin.ts:261:14 ❯ PuppeteerPlugin._launch node_modules/@crawlee/src/puppeteer/puppeteer-plugin.ts:88:21 ❯ Browser.start test/_helper.ts:13:24 ❯ test/key_value_stores.test.ts:19:9 Caused by: Caused by: Error: Could not find Chrome (ver. 146.0.7680.153). This can occur if either 1. you did not perform an installation before running the script (e.g. `npx puppeteer browsers install chrome`) or 2. your cache path is incorrectly configured (which is: /home/runner/.cache/puppeteer). For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration. ❯ ChromeLauncher.resolveExecutablePath node_modules/puppeteer-core/lib/cjs/puppeteer/node/BrowserLauncher.js:334:27 ❯ ChromeLauncher.computeLaunchArguments node_modules/puppeteer-core/lib/cjs/puppeteer/node/ChromeLauncher.js:94:24 ❯ ChromeLauncher.launch node_modules/puppeteer-core/lib/cjs/puppeteer/node/BrowserLauncher.js:85:28 ❯ PuppeteerPlugin._launch node_modules/@crawlee/browser-pool/puppeteer/puppeteer-plugin.js:52:27 ❯ Browser.start test/_helper.ts:13:24 ❯ test/key_value_stores.test.ts:19:9

BrowserLaunchError: Failed to launch browser. Please check the following: - Try installing a browser, if it's missing, by running `npx @puppeteer/browsers install chromium --path [path]` and pointing `executablePath` to the downloaded executable (https://pptr.dev/browsers-api) The original error is available in the `cause` property. Below is the error received when trying to launch a browser: ​ ❯ PuppeteerPlugin._throwAugmentedLaunchError node_modules/@crawlee/src/abstract-classes/browser-plugin.ts:261:14 ❯ PuppeteerPlugin._launch node_modules/@crawlee/src/puppeteer/puppeteer-plugin.ts:88:21 ❯ Browser.start test/_helper.ts:13:24 ❯ test/http_client.test.ts:16:9 Caused by: Caused by: Error: Could not find Chrome (ver. 146.0.7680.153). This can occur if either 1. you did not perform an installation before running the script (e.g. `npx puppeteer browsers install chrome`) or 2. your cache path is incorrectly configured (which is: /home/runner/.cache/puppeteer). For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration. ❯ ChromeLauncher.resolveExecutablePath node_modules/puppeteer-core/lib/cjs/puppeteer/node/BrowserLauncher.js:334:27 ❯ ChromeLauncher.computeLaunchArguments node_modules/puppeteer-core/lib/cjs/puppeteer/node/ChromeLauncher.js:94:24 ❯ ChromeLauncher.launch node_modules/puppeteer-core/lib/cjs/puppeteer/node/BrowserLauncher.js:85:28 ❯ PuppeteerPlugin._launch node_modules/@crawlee/browser-pool/puppeteer/puppeteer-plugin.js:52:27 ❯ Browser.start test/_helper.ts:13:24 ❯ test/http_client.test.ts:16:9

BrowserLaunchError: Failed to launch browser. Please check the following: - Try installing a browser, if it's missing, by running `npx @puppeteer/browsers install chromium --path [path]` and pointing `executablePath` to the downloaded executable (https://pptr.dev/browsers-api) The original error is available in the `cause` property. Below is the error received when trying to launch a browser: ​ ❯ PuppeteerPlugin._throwAugmentedLaunchError node_modules/@crawlee/src/abstract-classes/browser-plugin.ts:261:14 ❯ PuppeteerPlugin._launch node_modules/@crawlee/src/puppeteer/puppeteer-plugin.ts:88:21 ❯ Browser.start test/_helper.ts:13:24 ❯ test/datasets.test.ts:18:9 Caused by: Caused by: Error: Could not find Chrome (ver. 146.0.7680.153). This can occur if either 1. you did not perform an installation before running the script (e.g. `npx puppeteer browsers install chrome`) or 2. your cache path is incorrectly configured (which is: /home/runner/.cache/puppeteer). For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration. ❯ ChromeLauncher.resolveExecutablePath node_modules/puppeteer-core/lib/cjs/puppeteer/node/BrowserLauncher.js:334:27 ❯ ChromeLauncher.computeLaunchArguments node_modules/puppeteer-core/lib/cjs/puppeteer/node/ChromeLauncher.js:94:24 ❯ ChromeLauncher.launch node_modules/puppeteer-core/lib/cjs/puppeteer/node/BrowserLauncher.js:85:28 ❯ PuppeteerPlugin._launch node_modules/@crawlee/browser-pool/puppeteer/puppeteer-plugin.js:52:27 ❯ Browser.start test/_helper.ts:13:24 ❯ test/datasets.test.ts:18:9

BrowserLaunchError: Failed to launch browser. Please check the following: - Try installing a browser, if it's missing, by running `npx @puppeteer/browsers install chromium --path [path]` and pointing `executablePath` to the downloaded executable (https://pptr.dev/browsers-api) The original error is available in the `cause` property. Below is the error received when trying to launch a browser: ​ ❯ PuppeteerPlugin._throwAugmentedLaunchError node_modules/@crawlee/src/abstract-classes/browser-plugin.ts:261:14 ❯ PuppeteerPlugin._launch node_modules/@crawlee/src/puppeteer/puppeteer-plugin.ts:88:21 ❯ Browser.start test/_helper.ts:13:24 ❯ test/builds.test.ts:16:9 Caused by: Caused by: Error: Could not find Chrome (ver. 146.0.7680.153). This can occur if either 1. you did not perform an installation before running the script (e.g. `npx puppeteer browsers install chrome`) or 2. your cache path is incorrectly configured (which is: /home/runner/.cache/puppeteer). For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration. ❯ ChromeLauncher.resolveExecutablePath node_modules/puppeteer-core/lib/cjs/puppeteer/node/BrowserLauncher.js:334:27 ❯ ChromeLauncher.computeLaunchArguments node_modules/puppeteer-core/lib/cjs/puppeteer/node/ChromeLauncher.js:94:24 ❯ ChromeLauncher.launch node_modules/puppeteer-core/lib/cjs/puppeteer/node/BrowserLauncher.js:85:28 ❯ PuppeteerPlugin._launch node_modules/@crawlee/browser-pool/puppeteer/puppeteer-plugin.js:52:27 ❯ Browser.start test/_helper.ts:13:24 ❯ test/builds.test.ts:16:9

Error: Hook timed out in 10000ms. If this is a long-running hook, pass a timeout value as the last argument or configure it globally with "hookTimeout". ❯ test/apify_api_error.test.ts:20:5

BrowserLaunchError: Failed to launch browser. Please check the following: - Try installing a browser, if it's missing, by running `npx @puppeteer/browsers install chromium --path [path]` and pointing `executablePath` to the downloaded executable (https://pptr.dev/browsers-api) The original error is available in the `cause` property. Below is the error received when trying to launch a browser: ​ ❯ PuppeteerPlugin._throwAugmentedLaunchError node_modules/@crawlee/src/abstract-classes/browser-plugin.ts:261:14 ❯ PuppeteerPlugin._launch node_modules/@crawlee/src/puppeteer/puppeteer-plugin.ts:88:21 ❯ Browser.start test/_helper.ts:13:24 ❯ test/apify_api_error.test.ts:15:9 Caused by: Caused by: Error: Could not find Chrome (ver. 146.0.7680.153). This can occur if either 1. you did not perform an installation before running the script (e.g. `npx puppeteer browsers install chrome`) or 2. your cache path is incorrectly configured (which is: /home/runner/.cache/puppeteer). For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration. ❯ ChromeLauncher.resolveExecutablePath node_modules/puppeteer-core/lib/cjs/puppeteer/node/BrowserLauncher.js:334:27 ❯ ChromeLauncher.computeLaunchArguments node_modules/puppeteer-core/lib/cjs/puppeteer/node/ChromeLauncher.js:94:24 ❯ ChromeLauncher.launch node_modules/puppeteer-core/lib/cjs/puppeteer/node/BrowserLauncher.js:85:28 ❯ PuppeteerPlugin._launch node_modules/@crawlee/browser-pool/puppeteer/puppeteer-plugin.js:52:27 ❯ Browser.start test/_helper.ts:13:24 ❯ test/apify_api_error.test.ts:15:9

BrowserLaunchError: Failed to launch browser. Please check the following: - Try installing a browser, if it's missing, by running `npx @puppeteer/browsers install chromium --path [path]` and pointing `executablePath` to the downloaded executable (https://pptr.dev/browsers-api) The original error is available in the `cause` property. Below is the error received when trying to launch a browser: ​ ❯ PuppeteerPlugin._throwAugmentedLaunchError node_modules/@crawlee/src/abstract-classes/browser-plugin.ts:261:14 ❯ PuppeteerPlugin._launch node_modules/@crawlee/src/puppeteer/puppeteer-plugin.ts:88:21 ❯ Browser.start test/_helper.ts:13:24 ❯ test/actors.test.ts:26:9 Caused by: Caused by: Error: Could not find Chrome (ver. 146.0.7680.153). This can occur if either 1. you did not perform an installation before running the script (e.g. `npx puppeteer browsers install chrome`) or 2. your cache path is incorrectly configured (which is: /home/runner/.cache/puppeteer). For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration. ❯ ChromeLauncher.resolveExecutablePath node_modules/puppeteer-core/lib/cjs/puppeteer/node/BrowserLauncher.js:334:27 ❯ ChromeLauncher.computeLaunchArguments node_modules/puppeteer-core/lib/cjs/puppeteer/node/ChromeLauncher.js:94:24 ❯ ChromeLauncher.launch node_modules/puppeteer-core/lib/cjs/puppeteer/node/BrowserLauncher.js:85:28 ❯ PuppeteerPlugin._launch node_modules/@crawlee/browser-pool/puppeteer/puppeteer-plugin.js:52:27 ❯ Browser.start test/_helper.ts:13:24 ❯ test/actors.test.ts:26:9

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, pnpm/action-setup@v4.1.0. 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 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, pnpm/action-setup@v4.1.0. 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 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, pnpm/action-setup@v4.1.0. 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 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, pnpm/action-setup@v4.1.0. 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 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, pnpm/action-setup@v4.1.0. 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 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, pnpm/action-setup@v4.1.0. 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/