Skip to content

Replace AsyncAction with AsyncFetch #2055

Replace AsyncAction with AsyncFetch

Replace AsyncAction with AsyncFetch #2055

Triggered via push May 18, 2024 03:27
Status Failure
Total duration 2m 28s
Artifacts

ci.yml

on: push
Checks ๐Ÿ“  /  Lint ๐Ÿ’…
24s
Checks ๐Ÿ“ / Lint ๐Ÿ’…
Checks ๐Ÿ“  /  Type check ๐Ÿงฎ
1m 30s
Checks ๐Ÿ“ / Type check ๐Ÿงฎ
Checks ๐Ÿ“  /  Unit tests ๐Ÿงช
30s
Checks ๐Ÿ“ / Unit tests ๐Ÿงช
Matrix: Checks ๐Ÿ“ / End-to-end tests ๐Ÿ”ฌ
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 6 warnings
tests/e2e/async.test.ts > async > can server render with an async module: tests/e2e/async.test.ts#L32
AssertionError: expected '' to match 'Hello from an async module!' - Expected + Received - Hello from an async module! โฏ tests/e2e/async.test.ts:32:44
tests/e2e/async.test.ts > async > can server render an async component: tests/e2e/async.test.ts#L71
AssertionError: expected '' to match 'Hello from an async component!' - Expected + Received - Hello from an async component! โฏ tests/e2e/async.test.ts:71:44
tests/e2e/async.test.ts > async > can server render an async component with deferred hydration: tests/e2e/async.test.ts#L132
AssertionError: expected '' to match 'Hello from an async component!' - Expected + Received - Hello from an async component! โฏ tests/e2e/async.test.ts:132:44
tests/e2e/async.test.ts > async > can client render a client-only async component: tests/e2e/utilities.ts#L336
Error: page.goto: net::ERR_CONNECTION_REFUSED at http://localhost:33969/ =========================== logs =========================== navigating to "http://localhost:33969/", waiting until "load" ============================================================ โฏ Object.openPage tests/e2e/utilities.ts:336:18 โฏ tests/e2e/async.test.ts:330:22
Checks ๐Ÿ“ / End-to-end tests ๐Ÿ”ฌ (3/3)
Process completed with exit code 1.
Checks ๐Ÿ“ / Lint ๐Ÿ’…
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: pnpm/[email protected], actions/setup-node@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Checks ๐Ÿ“ / Unit tests ๐Ÿงช
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: pnpm/[email protected], actions/setup-node@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Checks ๐Ÿ“ / Type check ๐Ÿงฎ
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: pnpm/[email protected], actions/setup-node@v3, actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Checks ๐Ÿ“ / End-to-end tests ๐Ÿ”ฌ (1/3)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: pnpm/[email protected], actions/setup-node@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Checks ๐Ÿ“ / End-to-end tests ๐Ÿ”ฌ (2/3)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: pnpm/[email protected], actions/setup-node@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Checks ๐Ÿ“ / End-to-end tests ๐Ÿ”ฌ (3/3)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: pnpm/[email protected], actions/setup-node@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.