Skip to content

feat: Improved runtime compatibility #108

feat: Improved runtime compatibility

feat: Improved runtime compatibility #108

Triggered via pull request September 10, 2026 11:56
Status Failure
Total duration 16m 3s
Artifacts

ci.yml

on: pull_request
Build, lint, unit + integration tests
1m 31s
Build, lint, unit + integration tests
Matrix: e2e
Fit to window
Zoom out
Zoom in

Annotations

11 errors and 16 warnings
e2e dev-folder-bind-mount (apify-cli + podman-3.4)
Process completed with exit code 1.
test/e2e/dev-folder-bind-mount.test.ts > local dev-folder bind mount: edit-compile-call loop with no rebuild (requires Docker) > an entrypoint the image keeps inside its working directory (Apify's Playwright images start through one) stays available under the mount when the dev folder lacks it: test/e2e/dev-folder-bind-mount.test.ts#L351
AssertionError: expected '2026-09-10T12:00:02.688Z Mounting loc…' to contain 'only-in-dev-folder.txt' - Expected + Received - only-in-dev-folder.txt + 2026-09-10T12:00:02.688Z Mounting local dev folder /tmp/actor-runtime-e2e-devfolder-entry-src-NHKCzo over the image's working directory /app (node_modules preserved via a per-run volume). + 2026-09-10T12:00:02.921Z The image starts through ./entry.sh in its working directory, which the dev folder does not contain; using the image's own copy of it. + 2026-09-10T12:00:03.024Z entry.sh from the image: /apify-runtime-entrypoint/entry.sh + + ❯ test/e2e/dev-folder-bind-mount.test.ts:351:17
e2e dev-folder-bind-mount (apify-cli + podman)
Process completed with exit code 1.
test/e2e/dev-folder-bind-mount.test.ts > local dev-folder bind mount: edit-compile-call loop with no rebuild (requires Docker) > an entrypoint the image keeps inside its working directory (Apify's Playwright images start through one) stays available under the mount when the dev folder lacks it: test/e2e/dev-folder-bind-mount.test.ts#L351
AssertionError: expected '2026-09-10T12:00:01.657Z Mounting loc…' to contain 'only-in-dev-folder.txt' - Expected + Received - only-in-dev-folder.txt + 2026-09-10T12:00:01.657Z Mounting local dev folder /tmp/actor-runtime-e2e-devfolder-entry-src-lkdU9q over the image's working directory /app (node_modules preserved via a per-run volume). + 2026-09-10T12:00:01.804Z The image starts through ./entry.sh in its working directory, which the dev folder does not contain; using the image's own copy of it. + 2026-09-10T12:00:01.941Z entry.sh from the image: /apify-runtime-entrypoint/entry.sh + + ❯ test/e2e/dev-folder-bind-mount.test.ts:351:17
e2e dev-folder-bind-mount (apify-cli + docker)
Process completed with exit code 1.
test/e2e/dev-folder-bind-mount.test.ts > local dev-folder bind mount: edit-compile-call loop with no rebuild (requires Docker) > an entrypoint the image keeps inside its working directory (Apify's Playwright images start through one) stays available under the mount when the dev folder lacks it: test/e2e/dev-folder-bind-mount.test.ts#L351
AssertionError: expected '2026-09-10T12:00:20.115Z Mounting loc…' to contain 'only-in-dev-folder.txt' - Expected + Received - only-in-dev-folder.txt + 2026-09-10T12:00:20.115Z Mounting local dev folder /tmp/actor-runtime-e2e-devfolder-entry-src-KsxRoC over the image's working directory /app (node_modules preserved via a per-run volume). + 2026-09-10T12:00:20.144Z The image starts through ./entry.sh in its working directory, which the dev folder does not contain; using the image's own copy of it. + 2026-09-10T12:00:20.266Z entry.sh from the image: /apify-runtime-entrypoint/entry.sh + + ❯ test/e2e/dev-folder-bind-mount.test.ts:351:17
e2e browser-view-ts (apify-cli + docker)
Process completed with exit code 1.
e2e browser-view-ts (apify-cli + podman)
Process completed with exit code 1.
test/e2e/browser-view-ts.test.ts > per-Actor browser view: live mirror of the TypeScript Playwright sample Actor (requires Docker) > with the toggle cleared, a plain `apify call` of the same Actor runs exactly as before (no mirror, same crawl): test/e2e/helpers/apify-cli.ts#L11
Error: Command failed: npx -y -p apify-cli apify call --input {"maxRequestsPerCrawl":2} --memory 4096 --json npm warn Unknown env config "verify-deps-before-run". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options. Run: Calling Actor local-user-2/my-playwright-actor (IrZ93SJIhPW1Jmxv6) Started: 2026-09-10 at 12:07:45 Build: 0.0.1 (latest) | Actor version: 0.0 (latest) Timeout: 300 seconds Memory: 4096 MB View on Apify Console: http://localhost:3000/actors/IrZ93SJIhPW1Jmxv6/runs/mdlqs79rzirGHflWN 2026-09-10T12:07:45.712Z Running on architecture: x86_64 2026-09-10T12:07:45.712Z Will run command: xvfb-run -a -s "-ac -screen 0 1920x1080x24+32 -nolisten tcp" node dist/main.js 2026-09-10T12:07:46.676Z INFO System info {"apifyVersion":"3.7.2","apifyClientVersion":"2.25.0","crawleeVersion":"3.18.1","osType":"Linux","nodeVersion":"v24.21.0"} 2026-09-10T12:07:46.676Z INFO Crawling up to 2 page(s) with a headful Chrome, starting from https://crawlee.dev/. 2026-09-10T12:07:47.174Z INFO PlaywrightCrawler: Starting the crawler. 2026-09-10T12:08:47.174Z INFO PlaywrightCrawler:Statistics: PlaywrightCrawler request statistics: {"requestAvgFailedDurationMillis":null,"requestAvgFinishedDurationMillis":null,"requestsFinishedPerMinute":0,"requestsFailedPerMinute":0,"requestTotalDurationMillis":0,"requestsTotal":0,"crawlerRuntimeMillis":60306,"retryHistogram":[]} 2026-09-10T12:08:47.174Z INFO PlaywrightCrawler:AutoscaledPool: state {"currentConcurrency":1,"desiredConcurrency":1,"systemStatus":{"isSystemIdle":true,"memInfo":{"isOverloaded":false,"limitRatio":0.2,"actualRatio":0},"eventLoopInfo":{"isOverloaded":false,"limitRatio":0.6,"actualRatio":0},"cpuInfo":{"isOverloaded":false,"limitRatio":0.4,"actualRatio":0},"clientInfo":{"isOverloaded":false,"limitRatio":0.3,"actualRatio":0}}} 2026-09-10T12:08:48.924Z WARN PlaywrightCrawler: Reclaiming failed request back to the list or queue. page.goto: Timeout 60000ms exceeded. 2026-09-10T12:08:48.924Z Call log: 2026-09-10T12:08:48.924Z - navigating to "https://crawlee.dev/", waiting until "load" 2026-09-10T12:08:48.924Z 2026-09-10T12:08:48.924Z {"id":"3FULW9cbbkMrV4R","url":"https://crawlee.dev/","retryCount":1} 2026-09-10T12:09:47.174Z INFO PlaywrightCrawler:Statistics: PlaywrightCrawler request statistics: {"requestAvgFailedDurationMillis":null,"requestAvgFinishedDurationMillis":null,"requestsFinishedPerMinute":0,"requestsFailedPerMinute":0,"requestTotalDurationMillis":0,"requestsTotal":0,"crawlerRuntimeMillis":120306,"retryHistogram":[]} 2026-09-10T12:09:47.174Z INFO PlaywrightCrawler:AutoscaledPool: state {"currentConcurrency":1,"desiredConcurrency":1,"systemStatus":{"isSystemIdle":true,"memInfo":{"isOverloaded":false,"limitRatio":0.2,"actualRatio":0},"eventLoopInfo":{"isOverloaded":false,"limitRatio":0.6,"actualRatio":0},"cpuInfo":{"isOverloaded":false,"limitRatio":0.4,"actualRatio":0},"clientInfo":{"isOverloaded":false,"limitRatio":0.3,"actualRatio":0}}} 2026-09-10T12:09:48.924Z WARN PlaywrightCrawler: Reclaiming failed request back to the list or queue. page.goto: Timeout 60000ms exceeded. 2026-09-10T12:09:48.924Z Call log: 2026-09-10T12:09:48.924Z - navigating to "https://crawlee.dev/", waiting until "load" 2026-09-10T12:09:48.924Z 2026-09-10T12:09:48.924Z {"id":"3FULW9cbbkMrV4R","url":"https://crawlee.dev/","retryCount":2} 2026-09-10T12:10:24.424Z INFO PlaywrightCrawler: Processing https://crawlee.dev/ - Crawlee · Build reliable crawlers. Fast. 2026-09-10T12:10:47.174Z INFO PlaywrightCrawler:Statistics: PlaywrightCrawler request statistics: {"requestAvgFailedDurationMillis":null,"requestAvgFinishedDurationMillis":37486,"requestsFinishedPerMinute":0,"requestsFailedPerMinute":0,"requestTotalDurationMillis":37486,"requestsTotal":1,"crawlerRuntimeMillis":180305,"retryHistogram":[null,null,1]} 2026-09-10T12:10:47.174Z INFO PlaywrightCrawler:AutoscaledPool: state {"currentConcurrency":1,"desiredConcurrency":1,"systemStatus":{"isSystemIdle":true,"memInfo":{"isOverloaded":false,"limitRatio":0.2,"actualRatio":0},"eventLoop
Build, lint, unit + integration tests
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e browser-view-py (apify-cli + docker)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e browser-view-py (apify-cli + podman-3.4)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e browser-view-py (apify-cli + podman)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e debug-mode (apify-cli + podman)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e debug-mode (apify-cli + podman-3.4)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e actor-dev-loop (apify-cli + podman-3.4)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e debug-mode (apify-cli + docker)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e actor-dev-loop (apify-cli + podman)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e actor-dev-loop (apify-cli + docker)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e dev-folder-bind-mount (apify-cli + podman-3.4)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e dev-folder-bind-mount (apify-cli + podman)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e dev-folder-bind-mount (apify-cli + docker)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e browser-view-ts (apify-cli + podman-3.4)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e browser-view-ts (apify-cli + docker)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e browser-view-ts (apify-cli + podman)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/