feat: migrate analyze function to react-server-action
#4248
Annotations
1 error, 5 warnings, and 1 notice
e2e/ssr-swr.spec.ts#L58
1) [webkit] › ssr-swr.spec.ts:51:5 › ssr-swr: dev › increase counter ─────────────────────────────
Error: Timed out 10000ms waiting for expect(locator).toHaveText(expected)
Locator: getByTestId('count')
Expected string: "3"
Received string: "2"
Call log:
- expect.toHaveText with timeout 10000ms
- waiting for getByTestId('count')
- locator resolved to <p data-testid="count">2</p>
- unexpected value "2"
- locator resolved to <p data-testid="count">2</p>
- unexpected value "2"
- locator resolved to <p data-testid="count">2</p>
- unexpected value "2"
- locator resolved to <p data-testid="count">2</p>
- unexpected value "2"
- locator resolved to <p data-testid="count">2</p>
- unexpected value "2"
- locator resolved to <p data-testid="count">2</p>
- unexpected value "2"
- locator resolved to <p data-testid="count">2</p>
- unexpected value "2"
- locator resolved to <p data-testid="count">2</p>
- unexpected value "2"
- locator resolved to <p data-testid="count">2</p>
- unexpected value "2"
- locator resolved to <p data-testid="count">2</p>
- unexpected value "2"
- locator resolved to <p data-testid="count">2</p>
- unexpected value "2"
- locator resolved to <p data-testid="count">2</p>
- unexpected value "2"
- locator resolved to <p data-testid="count">2</p>
- unexpected value "2"
- locator resolved to <p data-testid="count">2</p>
- unexpected value "2"
56 | await page.getByTestId('increment').click();
57 | await page.getByTestId('increment').click();
> 58 | await expect(page.getByTestId('count')).toHaveText('3');
| ^
59 | });
60 |
61 | test('no js environment should have first screen', async ({ browser }) => {
at /home/runner/work/waku/waku/e2e/ssr-swr.spec.ts:58:47
|
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-node@v3, actions/cache@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
[webkit] › multi-platform.spec.ts#L1
[webkit] › multi-platform.spec.ts took 58.3s
|
[webkit] › ssg-performance.spec.ts#L1
[webkit] › ssg-performance.spec.ts took 29.2s
|
[webkit] › partial-builds.spec.ts#L1
[webkit] › partial-builds.spec.ts took 25.1s
|
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "playwright-report-macos-latest-18.17.0-1", "playwright-report-macos-latest-18.17.0-2", "playwright-report-macos-latest-18.17.0-3", "playwright-report-macos-latest-18.17.0-4", "playwright-report-macos-latest-20.8.0-1", "playwright-report-macos-latest-20.8.0-2", "playwright-report-macos-latest-20.8.0-3", "playwright-report-macos-latest-20.8.0-4", "playwright-report-ubuntu-latest-18.17.0-1", "playwright-report-ubuntu-latest-18.17.0-2", "playwright-report-ubuntu-latest-18.17.0-3", "playwright-report-ubuntu-latest-18.17.0-4", "playwright-report-ubuntu-latest-20.8.0-1", "playwright-report-ubuntu-latest-20.8.0-2", "playwright-report-ubuntu-latest-20.8.0-3", "playwright-report-ubuntu-latest-20.8.0-4", "playwright-report-windows-latest-18.17.0-1", "playwright-report-windows-latest-18.17.0-2", "playwright-report-windows-latest-18.17.0-3", "playwright-report-windows-latest-18.17.0-4", "playwright-report-windows-latest-20.8.0-1", "playwright-report-windows-latest-20.8.0-2", "playwright-report-windows-latest-20.8.0-4".
Please update your workflow to use v4 of the artifact actions.
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
|
|
This job succeeded
Loading