docs(env): add eval session setup guidance in .env.example #551
e2e.yml
on: push
Build
1m 20s
Matrix: e2e
Matrix: e2e-firefox
Matrix: e2e-webkit
Test Report
1m 21s
Annotations
16 errors, 29 warnings, and 1 notice
|
E2E (chromium-gen 3/6)
Process completed with exit code 1.
|
|
E2E (chromium-gen 2/6)
Process completed with exit code 1.
|
|
E2E (firefox-gen 2/6)
Process completed with exit code 1.
|
|
E2E (firefox-gen 3/6)
Process completed with exit code 1.
|
|
E2E (webkit-gen 3/6)
Process completed with exit code 1.
|
|
E2E (webkit-gen 2/6)
Process completed with exit code 1.
|
|
[chromium-gen] › tests/e2e/payment/02-paypal-subscription.spec.ts:69:7 › PayPal Subscription Creation Flow › should show PayPal payment button:
tests/e2e/payment/02-paypal-subscription.spec.ts#L79
4) [chromium-gen] › tests/e2e/payment/02-paypal-subscription.spec.ts:69:7 › PayPal Subscription Creation Flow › should show PayPal payment button
Error: expect(locator).toBeVisible() failed
Locator: getByRole('button', { name: /PayPal \$15\.00/i })
Expected: visible
Received: <element(s) not found>
Timeout: 5000ms
Call log:
- Expect "toBeVisible" with timeout 5000ms
- waiting for getByRole('button', { name: /PayPal \$15\.00/i })
77 | await expect(
78 | page.getByRole('button', { name: /PayPal \$15\.00/i })
> 79 | ).toBeVisible();
| ^
80 | });
81 |
82 | test.skip('should display subscription details correctly', async ({
at /home/runner/work/ScriptHammer/ScriptHammer/tests/e2e/payment/02-paypal-subscription.spec.ts:79:7
|
|
[chromium-gen] › tests/e2e/payment/02-paypal-subscription.spec.ts:53:7 › PayPal Subscription Creation Flow › should show PayPal provider tab:
tests/e2e/payment/02-paypal-subscription.spec.ts#L62
3) [chromium-gen] › tests/e2e/payment/02-paypal-subscription.spec.ts:53:7 › PayPal Subscription Creation Flow › should show PayPal provider tab
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: expect(locator).toBeVisible() failed
Locator: getByRole('tab', { name: /paypal/i }).first()
Expected: visible
Received: <element(s) not found>
Timeout: 5000ms
Call log:
- Expect "toBeVisible" with timeout 5000ms
- waiting for getByRole('tab', { name: /paypal/i }).first()
60 | // PayPal tab should be visible
61 | const paypalTab = page.getByRole('tab', { name: /paypal/i }).first();
> 62 | await expect(paypalTab).toBeVisible();
| ^
63 |
64 | // Click PayPal tab
65 | await paypalTab.click();
at /home/runner/work/ScriptHammer/ScriptHammer/tests/e2e/payment/02-paypal-subscription.spec.ts:62:29
|
|
[chromium-gen] › tests/e2e/payment/02-paypal-subscription.spec.ts:53:7 › PayPal Subscription Creation Flow › should show PayPal provider tab:
tests/e2e/payment/02-paypal-subscription.spec.ts#L62
3) [chromium-gen] › tests/e2e/payment/02-paypal-subscription.spec.ts:53:7 › PayPal Subscription Creation Flow › should show PayPal provider tab
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: expect(locator).toBeVisible() failed
Locator: getByRole('tab', { name: /paypal/i }).first()
Expected: visible
Received: <element(s) not found>
Timeout: 5000ms
Call log:
- Expect "toBeVisible" with timeout 5000ms
- waiting for getByRole('tab', { name: /paypal/i }).first()
60 | // PayPal tab should be visible
61 | const paypalTab = page.getByRole('tab', { name: /paypal/i }).first();
> 62 | await expect(paypalTab).toBeVisible();
| ^
63 |
64 | // Click PayPal tab
65 | await paypalTab.click();
at /home/runner/work/ScriptHammer/ScriptHammer/tests/e2e/payment/02-paypal-subscription.spec.ts:62:29
|
|
[chromium-gen] › tests/e2e/payment/02-paypal-subscription.spec.ts:53:7 › PayPal Subscription Creation Flow › should show PayPal provider tab:
tests/e2e/payment/02-paypal-subscription.spec.ts#L62
3) [chromium-gen] › tests/e2e/payment/02-paypal-subscription.spec.ts:53:7 › PayPal Subscription Creation Flow › should show PayPal provider tab
Error: expect(locator).toBeVisible() failed
Locator: getByRole('tab', { name: /paypal/i }).first()
Expected: visible
Received: <element(s) not found>
Timeout: 5000ms
Call log:
- Expect "toBeVisible" with timeout 5000ms
- waiting for getByRole('tab', { name: /paypal/i }).first()
60 | // PayPal tab should be visible
61 | const paypalTab = page.getByRole('tab', { name: /paypal/i }).first();
> 62 | await expect(paypalTab).toBeVisible();
| ^
63 |
64 | // Click PayPal tab
65 | await paypalTab.click();
at /home/runner/work/ScriptHammer/ScriptHammer/tests/e2e/payment/02-paypal-subscription.spec.ts:62:29
|
|
[chromium-gen] › tests/e2e/payment/01-stripe-onetime.spec.ts:133:7 › Stripe One-Time Payment Flow › should allow selecting different payment providers:
tests/e2e/payment/01-stripe-onetime.spec.ts#L144
2) [chromium-gen] › tests/e2e/payment/01-stripe-onetime.spec.ts:133:7 › Stripe One-Time Payment Flow › should allow selecting different payment providers
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
TimeoutError: locator.click: Timeout 15000ms exceeded.
Call log:
- waiting for getByRole('tab', { name: /stripe/i }).first()
142 | // Select Stripe tab
143 | const stripeTab = page.getByRole('tab', { name: /stripe/i }).first();
> 144 | await stripeTab.click();
| ^
145 | await expect(stripeTab).toHaveClass(/tab-active/);
146 |
147 | // Select PayPal tab
at /home/runner/work/ScriptHammer/ScriptHammer/tests/e2e/payment/01-stripe-onetime.spec.ts:144:21
|
|
[chromium-gen] › tests/e2e/payment/01-stripe-onetime.spec.ts:133:7 › Stripe One-Time Payment Flow › should allow selecting different payment providers:
tests/e2e/payment/01-stripe-onetime.spec.ts#L144
2) [chromium-gen] › tests/e2e/payment/01-stripe-onetime.spec.ts:133:7 › Stripe One-Time Payment Flow › should allow selecting different payment providers
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
TimeoutError: locator.click: Timeout 15000ms exceeded.
Call log:
- waiting for getByRole('tab', { name: /stripe/i }).first()
142 | // Select Stripe tab
143 | const stripeTab = page.getByRole('tab', { name: /stripe/i }).first();
> 144 | await stripeTab.click();
| ^
145 | await expect(stripeTab).toHaveClass(/tab-active/);
146 |
147 | // Select PayPal tab
at /home/runner/work/ScriptHammer/ScriptHammer/tests/e2e/payment/01-stripe-onetime.spec.ts:144:21
|
|
[chromium-gen] › tests/e2e/payment/01-stripe-onetime.spec.ts:133:7 › Stripe One-Time Payment Flow › should allow selecting different payment providers:
tests/e2e/payment/01-stripe-onetime.spec.ts#L144
2) [chromium-gen] › tests/e2e/payment/01-stripe-onetime.spec.ts:133:7 › Stripe One-Time Payment Flow › should allow selecting different payment providers
TimeoutError: locator.click: Timeout 15000ms exceeded.
Call log:
- waiting for getByRole('tab', { name: /stripe/i }).first()
142 | // Select Stripe tab
143 | const stripeTab = page.getByRole('tab', { name: /stripe/i }).first();
> 144 | await stripeTab.click();
| ^
145 | await expect(stripeTab).toHaveClass(/tab-active/);
146 |
147 | // Select PayPal tab
at /home/runner/work/ScriptHammer/ScriptHammer/tests/e2e/payment/01-stripe-onetime.spec.ts:144:21
|
|
[chromium-gen] › tests/e2e/payment/01-stripe-onetime.spec.ts:108:7 › Stripe One-Time Payment Flow › should show payment options after granting consent:
tests/e2e/payment/01-stripe-onetime.spec.ts#L122
1) [chromium-gen] › tests/e2e/payment/01-stripe-onetime.spec.ts:108:7 › Stripe One-Time Payment Flow › should show payment options after granting consent
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: expect(locator).toBeVisible() failed
Locator: getByRole('tab', { name: /stripe/i }).first()
Expected: visible
Received: <element(s) not found>
Timeout: 5000ms
Call log:
- Expect "toBeVisible" with timeout 5000ms
- waiting for getByRole('tab', { name: /stripe/i }).first()
120 | await expect(
121 | page.getByRole('tab', { name: /stripe/i }).first()
> 122 | ).toBeVisible();
| ^
123 | await expect(
124 | page.getByRole('tab', { name: /paypal/i }).first()
125 | ).toBeVisible();
at /home/runner/work/ScriptHammer/ScriptHammer/tests/e2e/payment/01-stripe-onetime.spec.ts:122:7
|
|
[chromium-gen] › tests/e2e/payment/01-stripe-onetime.spec.ts:108:7 › Stripe One-Time Payment Flow › should show payment options after granting consent:
tests/e2e/payment/01-stripe-onetime.spec.ts#L122
1) [chromium-gen] › tests/e2e/payment/01-stripe-onetime.spec.ts:108:7 › Stripe One-Time Payment Flow › should show payment options after granting consent
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: expect(locator).toBeVisible() failed
Locator: getByRole('tab', { name: /stripe/i }).first()
Expected: visible
Received: <element(s) not found>
Timeout: 5000ms
Call log:
- Expect "toBeVisible" with timeout 5000ms
- waiting for getByRole('tab', { name: /stripe/i }).first()
120 | await expect(
121 | page.getByRole('tab', { name: /stripe/i }).first()
> 122 | ).toBeVisible();
| ^
123 | await expect(
124 | page.getByRole('tab', { name: /paypal/i }).first()
125 | ).toBeVisible();
at /home/runner/work/ScriptHammer/ScriptHammer/tests/e2e/payment/01-stripe-onetime.spec.ts:122:7
|
|
[chromium-gen] › tests/e2e/payment/01-stripe-onetime.spec.ts:108:7 › Stripe One-Time Payment Flow › should show payment options after granting consent:
tests/e2e/payment/01-stripe-onetime.spec.ts#L122
1) [chromium-gen] › tests/e2e/payment/01-stripe-onetime.spec.ts:108:7 › Stripe One-Time Payment Flow › should show payment options after granting consent
Error: expect(locator).toBeVisible() failed
Locator: getByRole('tab', { name: /stripe/i }).first()
Expected: visible
Received: <element(s) not found>
Timeout: 5000ms
Call log:
- Expect "toBeVisible" with timeout 5000ms
- waiting for getByRole('tab', { name: /stripe/i }).first()
120 | await expect(
121 | page.getByRole('tab', { name: /stripe/i }).first()
> 122 | ).toBeVisible();
| ^
123 | await expect(
124 | page.getByRole('tab', { name: /paypal/i }).first()
125 | ).toBeVisible();
at /home/runner/work/ScriptHammer/ScriptHammer/tests/e2e/payment/01-stripe-onetime.spec.ts:122:7
|
|
Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@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/
|
|
Smoke Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, pnpm/action-setup@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/
|
|
Auth Setup
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@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/
|
|
Rate-Limiting Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, pnpm/action-setup@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 (chromium-gen 5/6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@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 (chromium-gen 1/6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@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 (chromium-gen 6/6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@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 (chromium-gen 4/6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@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 (chromium-gen 3/6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@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 (chromium-gen 2/6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@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 (chromium-msg 1/2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@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 (chromium-msg 2/2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@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 (firefox-gen 6/6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@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 (firefox-gen 1/6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@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 (firefox-gen 4/6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@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 (firefox-gen 2/6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@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 (firefox-gen 5/6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@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 (firefox-msg 1/2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@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 (firefox-msg 2/2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@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 (firefox-gen 3/6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@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 (webkit-gen 5/6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@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 (webkit-gen 1/6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@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 (webkit-gen 6/6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@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 (webkit-gen 3/6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@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 (webkit-gen 4/6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@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 (webkit-gen 2/6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@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 (webkit-msg 1/2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@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 (webkit-msg 2/2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@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/
|
|
Test Report
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@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/
|
|
🎭 Playwright Run Summary
18 failed
[chromium-gen] › tests/e2e/payment/01-stripe-onetime.spec.ts:108:7 › Stripe One-Time Payment Flow › should show payment options after granting consent
[chromium-gen] › tests/e2e/payment/01-stripe-onetime.spec.ts:133:7 › Stripe One-Time Payment Flow › should allow selecting different payment providers
[chromium-gen] › tests/e2e/payment/02-paypal-subscription.spec.ts:53:7 › PayPal Subscription Creation Flow › should show PayPal provider tab
[chromium-gen] › tests/e2e/payment/02-paypal-subscription.spec.ts:69:7 › PayPal Subscription Creation Flow › should show PayPal payment button
[firefox-gen] › tests/e2e/payment/01-stripe-onetime.spec.ts:108:7 › Stripe One-Time Payment Flow › should show payment options after granting consent
[firefox-gen] › tests/e2e/payment/01-stripe-onetime.spec.ts:133:7 › Stripe One-Time Payment Flow › should allow selecting different payment providers
[firefox-gen] › tests/e2e/payment/02-paypal-subscription.spec.ts:53:7 › PayPal Subscription Creation Flow › should show PayPal provider tab
[firefox-gen] › tests/e2e/payment/02-paypal-subscription.spec.ts:69:7 › PayPal Subscription Creation Flow › should show PayPal payment button
[webkit-gen] › tests/e2e/payment/01-stripe-onetime.spec.ts:108:7 › Stripe One-Time Payment Flow › should show payment options after granting consent
[webkit-gen] › tests/e2e/payment/01-stripe-onetime.spec.ts:133:7 › Stripe One-Time Payment Flow › should allow selecting different payment providers
[webkit-gen] › tests/e2e/payment/02-paypal-subscription.spec.ts:53:7 › PayPal Subscription Creation Flow › should show PayPal provider tab
[webkit-gen] › tests/e2e/payment/02-paypal-subscription.spec.ts:69:7 › PayPal Subscription Creation Flow › should show PayPal payment button
[chromium-gen] › tests/e2e/payment/03-failed-payment-retry.spec.ts:110:7 › Failed Payment Retry Logic › should grant consent and show payment options
[chromium-gen] › tests/e2e/payment/04-gdpr-consent.spec.ts:82:7 › GDPR Payment Consent Flow › should show payment options after consent granted
[firefox-gen] › tests/e2e/payment/03-failed-payment-retry.spec.ts:110:7 › Failed Payment Retry Logic › should grant consent and show payment options
[firefox-gen] › tests/e2e/payment/04-gdpr-consent.spec.ts:82:7 › GDPR Payment Consent Flow › should show payment options after consent granted
[webkit-gen] › tests/e2e/payment/03-failed-payment-retry.spec.ts:110:7 › Failed Payment Retry Logic › should grant consent and show payment options
[webkit-gen] › tests/e2e/payment/04-gdpr-consent.spec.ts:82:7 › GDPR Payment Consent Flow › should show payment options after consent granted
10 flaky
[chromium-msg] › tests/e2e/messaging/encrypted-messaging.spec.ts:483:7 › Encrypted Messaging Flow › should show delivery status indicators
[chromium-msg] › tests/e2e/messaging/friend-requests.spec.ts:200:7 › Friend Request Flow › User A sends friend request and User B accepts
[chromium-msg] › tests/e2e/messaging/friend-requests.spec.ts:534:7 › Friend Request Flow › User cannot send duplicate requests
[firefox-msg] › tests/e2e/messaging/encrypted-messaging.spec.ts:177:7 › Encrypted Messaging Flow › should send and receive encrypted message between two users
[webkit-msg] › tests/e2e/messaging/encrypted-messaging.spec.ts:177:7 › Encrypted Messaging Flow › should send and receive encrypted message between two users
[chromium-msg] › tests/e2e/messaging/real-time-delivery.spec.ts:307:7 › Real-time Message Delivery (T098) › should show delivery status (sent → delivered → read)
[firefox-msg] › tests/e2e/messaging/message-delete-placeholder.spec.ts:341:7 › Message Delete Placeholder E2E › should show [Message deleted] placeholder and preserve adjacent messages
[firefox-msg] › tests/e2e/messaging/real-time-delivery.spec.ts:279:7 › Real-time Message Deliver
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
auth-state
Expired
|
1.7 KB |
sha256:d1e16d1c7c5874330ffc42fd2c180fd3718783f32dea9a2273239f82bb03f167
|
|
|
blob-report-chromium-gen-2
Expired
|
8.3 MB |
sha256:08b9dc34c70b5fd7a892b46183d2c696f86df735d4f1d05eabf9f99cd4f9ef55
|
|
|
blob-report-chromium-gen-3
Expired
|
44.9 MB |
sha256:348d318c857be4b0524ffacec2c45bb14f22b94c68df9a4041187e1d40ab60d0
|
|
|
blob-report-chromium-gen-4
Expired
|
18.2 MB |
sha256:3bd17b556a854ec1e90daf9f51e1800d962a3b1dd6cc92154fbfc169fc0da149
|
|
|
blob-report-chromium-gen-5
Expired
|
10.9 MB |
sha256:483199a9e34287074d089d403e2a9d9111b18e4d9d7c8ffa4e771b046399469f
|
|
|
blob-report-chromium-gen-6
Expired
|
6.8 MB |
sha256:0bc1ca7f433a5b3f964a250127cf12794fb97418d735aa8a531a05b53b022cd6
|
|
|
blob-report-chromium-gen-7
Expired
|
8.41 MB |
sha256:d422d01f2358208aae3b2a5782dab63d25021e6fce9afa0dcf618d010061af0e
|
|
|
blob-report-chromium-msg-0
Expired
|
69.6 MB |
sha256:d8c55a3da91e281c61d8538b2632ac88fb487571994ac118d98f2e7599054117
|
|
|
blob-report-chromium-msg-1
Expired
|
140 MB |
sha256:414d6470904488e8f8869e1622fa124a1102de38c7db1bae97763bf5bbe36173
|
|
|
blob-report-firefox-gen-2
Expired
|
6.62 MB |
sha256:498df92a9aaef2ab924ccbad4125b9cfd09176a2e99b287dd800e165174fe093
|
|
|
blob-report-firefox-gen-3
Expired
|
41.8 MB |
sha256:8d2d05f8b152f20b31f4ba0da8ad773d2aed2abc118090aef62667727a0793f2
|
|
|
blob-report-firefox-gen-4
Expired
|
15 MB |
sha256:7c278e22a99104f9e6c353d20c13540d337db11935a3deb18d70f779b6787393
|
|
|
blob-report-firefox-gen-5
Expired
|
11.9 MB |
sha256:5995700725d3aecca01da4e0863eb8774e9d007fe3ff11e83c919c818130ccd9
|
|
|
blob-report-firefox-gen-6
Expired
|
7.7 MB |
sha256:76f5c2872afeac65eba0d42645f0cb4c52983a4044c86a1710804879390aefc9
|
|
|
blob-report-firefox-gen-7
Expired
|
9.81 MB |
sha256:b3bed34138b7b19ff4759bf5c2b5396107571a464d16275c2ccf12b291575271
|
|
|
blob-report-firefox-msg-0
Expired
|
59.3 MB |
sha256:4cd61f10ebd5430e2ff76863389f31109e181ef601151afd418dae258a2eb7e5
|
|
|
blob-report-firefox-msg-1
Expired
|
153 MB |
sha256:c7a53d950cd97df69f747b117968bf48e7a79d58f5d8a698afd602359e736b06
|
|
|
blob-report-webkit-gen-2
Expired
|
19 MB |
sha256:276aa8c8f23fdd44c6973697b1a04a90293998fb289331e00c07057d51f27e70
|
|
|
blob-report-webkit-gen-3
Expired
|
91.3 MB |
sha256:b1bcc0fda2db83f11cd359f13cd291415bdba5ec66c5bf594f03b987be644738
|
|
|
blob-report-webkit-gen-4
Expired
|
41.2 MB |
sha256:5b2e9c14f86c4bc1f6ead4fdc36c3baadacfc833c815b09a4bacb6b7761af4c8
|
|
|
blob-report-webkit-gen-5
Expired
|
34.3 MB |
sha256:fab023ad15acf122b92bfa3dfd458e456a337932820969b67e5eb9c2d63a6018
|
|
|
blob-report-webkit-gen-6
Expired
|
19 MB |
sha256:f2b333f6380b9580c4b0eab3b9dd898060a2194349de11d8dbbe5f7f13029373
|
|
|
blob-report-webkit-gen-7
Expired
|
19.5 MB |
sha256:9fd59f46d147a2a57358d7a4dbfa02fcfcca7be996ef558da7c9dccc837e331c
|
|
|
blob-report-webkit-msg-0
Expired
|
47.7 MB |
sha256:4189f2872fa397207748f194de128d6e57e1d844a546806c5c3f816f79a13003
|
|
|
blob-report-webkit-msg-1
Expired
|
125 MB |
sha256:b836a7fba7d82532891af8e568e5675f2aca390165970564366bc0b7cf29ea45
|
|
|
build-output
Expired
|
17.3 MB |
sha256:0f8f86a6410e6138fe98e89ebd4a6131ee3e57651743d03743fab0a61ab82735
|
|
|
playwright-report
Expired
|
1000 MB |
sha256:b004368b617628db87ba0d7ee45300077b2860434bb2974ee62fbdd244ca710c
|
|