Skip to content

feat(browser): adopt lightpanda via browser-manager subsystem #2

feat(browser): adopt lightpanda via browser-manager subsystem

feat(browser): adopt lightpanda via browser-manager subsystem #2

Triggered via pull request April 7, 2026 14:57
@jadbjadb
synchronize #24
adopt-lightpanda
Status Failure
Total duration 2m 24s
Artifacts

e2e-playwright.yml

on: pull_request
Matrix: e2e-fast
e2e:full — ubuntu
e2e:full — ubuntu
Fit to window
Zoom out
Zoom in

Annotations

14 errors and 3 warnings
e2e:fast — windows-latest
Process completed with exit code 1.
e2e:fast — ubuntu-latest
Process completed with exit code 1.
test/e2e/sdk-export.test.js > sdk-export — CLI subprocess exits cleanly (story 037) > ibr --help exits 0 and prints usage: test/e2e/sdk-export.test.js#L232
AssertionError: expected '' to match /ibr|usage|instructions/i - Expected: /ibr|usage|instructions/i + Received: "" ❯ test/e2e/sdk-export.test.js:232:24
test/e2e/cli-non-interactive.test.js > cli composition via stdin (story 033) > multiline stdin prompt accepted intact → exit 0: test/e2e/cli-non-interactive.test.js#L151
ReferenceError: startFakeAIServerE2E is not defined ❯ test/e2e/cli-non-interactive.test.js:151:18
test/e2e/cli-cache-reuse.test.js > cli cache reuse across runs (story 031) > XDG_CACHE_HOME respected when CACHE_DIR not set → run exits 0: test/e2e/cli-cache-reuse.test.js#L228
AssertionError: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ test/e2e/cli-cache-reuse.test.js:228:29
e2e:fast — macos-latest
Process completed with exit code 1.
test/e2e/sdk-export.test.js > sdk-export — CLI subprocess exits cleanly (story 037) > ibr --help exits 0 and prints usage: test/e2e/sdk-export.test.js#L232
AssertionError: expected '' to match /ibr|usage|instructions/i - Expected: /ibr|usage|instructions/i + Received: "" ❯ test/e2e/sdk-export.test.js:232:24
test/e2e/cli-non-interactive.test.js > cli composition via stdin (story 033) > multiline stdin prompt accepted intact → exit 0: test/e2e/cli-non-interactive.test.js#L151
ReferenceError: startFakeAIServerE2E is not defined ❯ test/e2e/cli-non-interactive.test.js:151:18
e2e:fast — windows-latest
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. 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/
e2e:fast — ubuntu-latest
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. 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/
e2e:fast — macos-latest
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. 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/