1) [chromium] › tests/pi-durable.test.ts:23:1 › traces a run as invoke_agent with chat, execute_tool and provider spans Error: expect(received).toContain(expected) // indexOf Expected substring: "21 degrees and sunny in" Received string: "" 92 | expect(tool.status).toBe('ok'); 93 | expect(tool.attributes[GEN_AI_TOOL_CALL_ARGUMENTS]?.value).toContain('Vienna'); > 94 | expect(tool.attributes[GEN_AI_TOOL_CALL_RESULT]?.value).toContain('21 degrees and sunny in'); | ^ 95 | 96 | // The provider's HTTP calls nest inside the `chat` span that sent them. 97 | expect(providerCalls.length).toBeGreaterThan(0); at /home/runner/work/_temp/test-application/tests/pi-durable.test.ts:94:59

E2E cloudflare-pi-durable (latest) Test (optional)

Process completed with exit code 1.

[chromium] › tests/pi-durable.test.ts:21:5 › traces a PiHarness prompt as invoke_agent with chat: ../../_temp/test-application/tests/pi-durable.test.ts#L78

1) [chromium] › tests/pi-durable.test.ts:21:5 › traces a PiHarness prompt as invoke_agent with chat, execute_tool and provider spans Error: expect(received).toContain(expected) // indexOf Expected substring: "21 degrees and sunny in" Received string: "" 76 | expect(tool.status).toBe('ok'); 77 | expect(tool.attributes[GEN_AI_TOOL_CALL_ARGUMENTS]?.value).toContain('Vienna'); > 78 | expect(tool.attributes[GEN_AI_TOOL_CALL_RESULT]?.value).toContain('21 degrees and sunny in'); | ^ 79 | 80 | // The provider's HTTP calls nest inside the `chat` span that sent them. 81 | expect(providerCalls.length).toBeGreaterThan(0); at /home/runner/work/_temp/test-application/tests/pi-durable.test.ts:78:59

Bun (1.4) Integration Tests (2/2)

Process completed with exit code 1.

[node-suites-bun-build] suites/tracing/pi-durable/test.ts > pi-durable integration > nests subagent runs under the tool call that started them [esm]: dev-packages/node-integration-tests/utils/runner/createEsmAndCjsTests.ts#L385

Error: Test timed out in 45000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ Object.apply utils/runner/createEsmAndCjsTests.ts:385:22 ❯ suites/tracing/pi-durable/test.ts:418:7 ❯ createEsmAndCjsTests utils/runner/createEsmAndCjsTests.ts:64:3 ❯ suites/tracing/pi-durable/test.ts:409:3

[node-suites-bun-build] suites/tracing/pi-durable/test.ts > pi-durable integration > records the tool result the model receives [esm]: dev-packages/node-integration-tests/utils/runner/createEsmAndCjsTests.ts#L385

Error: Test timed out in 45000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ Object.apply utils/runner/createEsmAndCjsTests.ts:385:22 ❯ suites/tracing/pi-durable/test.ts:300:7 ❯ createEsmAndCjsTests utils/runner/createEsmAndCjsTests.ts:64:3 ❯ suites/tracing/pi-durable/test.ts:256:3

[node-suites-bun-build] suites/tracing/pi-durable/test.ts > pi-durable integration > traces each run as its own invoke_agent trace with chat and execute_tool children [esm]: dev-packages/node-integration-tests/utils/runner/createEsmAndCjsTests.ts#L385

Error: Test timed out in 45000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ Object.apply utils/runner/createEsmAndCjsTests.ts:385:22 ❯ suites/tracing/pi-durable/test.ts:63:7 ❯ createEsmAndCjsTests utils/runner/createEsmAndCjsTests.ts:64:3 ❯ suites/tracing/pi-durable/test.ts:53:3

Bun (1.3.14) Integration Tests (2/2)

Process completed with exit code 1.

Error: Test timed out in 45000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ Object.apply utils/runner/createEsmAndCjsTests.ts:385:22 ❯ suites/tracing/pi-durable/test.ts:300:7 ❯ createEsmAndCjsTests utils/runner/createEsmAndCjsTests.ts:64:3 ❯ suites/tracing/pi-durable/test.ts:256:3

Error: Test timed out in 45000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ Object.apply utils/runner/createEsmAndCjsTests.ts:385:22 ❯ suites/tracing/pi-durable/test.ts:63:7 ❯ createEsmAndCjsTests utils/runner/createEsmAndCjsTests.ts:64:3 ❯ suites/tracing/pi-durable/test.ts:53:3

Node (26) Integration Tests (2/3)

Process completed with exit code 1.

suites/tracing/pi-durable/test.ts > pi-durable integration > nests subagent runs under the tool call that started them [esm]: dev-packages/node-integration-tests/utils/runner/createEsmAndCjsTests.ts#L385

Error: Test timed out in 15000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ Object.apply utils/runner/createEsmAndCjsTests.ts:385:22 ❯ suites/tracing/pi-durable/test.ts:418:7 ❯ createEsmAndCjsTests utils/runner/createEsmAndCjsTests.ts:64:3 ❯ suites/tracing/pi-durable/test.ts:409:3

suites/tracing/pi-durable/test.ts > pi-durable integration > records the tool result the model receives [esm]: dev-packages/node-integration-tests/utils/runner/createEsmAndCjsTests.ts#L385

Error: Test timed out in 15000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ Object.apply utils/runner/createEsmAndCjsTests.ts:385:22 ❯ suites/tracing/pi-durable/test.ts:300:7 ❯ createEsmAndCjsTests utils/runner/createEsmAndCjsTests.ts:64:3 ❯ suites/tracing/pi-durable/test.ts:256:3

suites/tracing/pi-durable/test.ts > pi-durable integration > traces each run as its own invoke_agent trace with chat and execute_tool children [esm]: dev-packages/node-integration-tests/utils/runner/createEsmAndCjsTests.ts#L385

Error: Test timed out in 15000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ Object.apply utils/runner/createEsmAndCjsTests.ts:385:22 ❯ suites/tracing/pi-durable/test.ts:63:7 ❯ createEsmAndCjsTests utils/runner/createEsmAndCjsTests.ts:64:3 ❯ suites/tracing/pi-durable/test.ts:53:3

Deno Integration Tests (2/2)

Process completed with exit code 1.

suites/tracing/pi-durable/test.ts > pi-durable integration > records the tool result the model receives [esm]: dev-packages/node-integration-tests/utils/runner/createEsmAndCjsTests.ts#L385

Error: Test timed out in 45000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ Object.apply utils/runner/createEsmAndCjsTests.ts:385:22 ❯ suites/tracing/pi-durable/test.ts:300:7 ❯ createEsmAndCjsTests utils/runner/createEsmAndCjsTests.ts:64:3 ❯ suites/tracing/pi-durable/test.ts:256:3

Error: Test timed out in 45000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ Object.apply utils/runner/createEsmAndCjsTests.ts:385:22 ❯ suites/tracing/pi-durable/test.ts:63:7 ❯ createEsmAndCjsTests utils/runner/createEsmAndCjsTests.ts:64:3 ❯ suites/tracing/pi-durable/test.ts:53:3

Node (24) Integration Tests (2/3)

Process completed with exit code 1.

suites/tracing/pi-durable/test.ts > pi-durable integration > records the tool result the model receives [esm]: dev-packages/node-integration-tests/utils/runner/createEsmAndCjsTests.ts#L385

Error: Test timed out in 15000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ Object.apply utils/runner/createEsmAndCjsTests.ts:385:22 ❯ suites/tracing/pi-durable/test.ts:300:7 ❯ createEsmAndCjsTests utils/runner/createEsmAndCjsTests.ts:64:3 ❯ suites/tracing/pi-durable/test.ts:256:3

Error: Test timed out in 15000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ Object.apply utils/runner/createEsmAndCjsTests.ts:385:22 ❯ suites/tracing/pi-durable/test.ts:63:7 ❯ createEsmAndCjsTests utils/runner/createEsmAndCjsTests.ts:64:3 ❯ suites/tracing/pi-durable/test.ts:53:3

Node (22) Integration Tests (2/3)

Process completed with exit code 1.

suites/tracing/pi-durable/test.ts > pi-durable integration > records the tool result the model receives [esm]: dev-packages/node-integration-tests/utils/runner/createEsmAndCjsTests.ts#L385

Error: Test timed out in 15000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ Object.apply utils/runner/createEsmAndCjsTests.ts:385:22 ❯ suites/tracing/pi-durable/test.ts:300:7 ❯ createEsmAndCjsTests utils/runner/createEsmAndCjsTests.ts:64:3 ❯ suites/tracing/pi-durable/test.ts:256:3

Error: Test timed out in 15000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ Object.apply utils/runner/createEsmAndCjsTests.ts:385:22 ❯ suites/tracing/pi-durable/test.ts:63:7 ❯ createEsmAndCjsTests utils/runner/createEsmAndCjsTests.ts:64:3 ❯ suites/tracing/pi-durable/test.ts:53:3

Node (24) (TS 5.0) Integration Tests (2/3)

Process completed with exit code 1.

suites/tracing/pi-durable/test.ts > pi-durable integration > records the tool result the model receives [esm]: dev-packages/node-integration-tests/utils/runner/createEsmAndCjsTests.ts#L385

Error: Test timed out in 15000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ Object.apply utils/runner/createEsmAndCjsTests.ts:385:22 ❯ suites/tracing/pi-durable/test.ts:300:7 ❯ createEsmAndCjsTests utils/runner/createEsmAndCjsTests.ts:64:3 ❯ suites/tracing/pi-durable/test.ts:256:3

Error: Test timed out in 15000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ Object.apply utils/runner/createEsmAndCjsTests.ts:385:22 ❯ suites/tracing/pi-durable/test.ts:63:7 ❯ createEsmAndCjsTests utils/runner/createEsmAndCjsTests.ts:64:3 ❯ suites/tracing/pi-durable/test.ts:53:3

All required jobs passed or were skipped

Process completed with exit code 1.

[chromium] › tests/cacheOriginLinks-nesting.spec.ts:55:5 › links a cached leaf component under dynamic layouts to the trace that filled the leaf entry: ../../_temp/test-application/tests/cacheOriginLinks-nesting.spec.ts#L0

10) [chromium] › tests/cacheOriginLinks-nesting.spec.ts:55:5 › links a cached leaf component under dynamic layouts to the trace that filled the leaf entry Test timeout of 30000ms exceeded.

[chromium] › tests/cacheOriginLinks-nesting.spec.ts:11:5 › links a cached layout hit to the trace that filled the layout entry: ../../_temp/test-application/tests/cacheOriginLinks-nesting.spec.ts#L0

9) [chromium] › tests/cacheOriginLinks-nesting.spec.ts:11:5 › links a cached layout hit to the trace that filled the layout entry Test timeout of 30000ms exceeded.

[chromium] › tests/cacheComponents.spec.ts:116:5 › Should prerender a page that captures an exception in generateMetadata: ../../_temp/test-application/tests/cacheComponents.spec.ts#L119

8) [chromium] › tests/cacheComponents.spec.ts:116:5 › Should prerender a page that captures an exception in generateMetadata Error: expect(page).toHaveTitle(expected) failed Expected: "capture-metadata" Received: "An error has occurred" Timeout: 10000ms Call log: - Expect "toHaveTitle" with timeout 10000ms 16 × locator resolved to <html lang="en" class="light">…</html> - unexpected value "An error has occurred" 117 | await page.goto('/capture-metadata'); 118 | > 119 | await expect(page).toHaveTitle('capture-metadata'); | ^ 120 | await expect(page.locator('h1')).toHaveText('capture-metadata'); 121 | }); 122 | at /home/runner/work/_temp/test-application/tests/cacheComponents.spec.ts:119:22

[chromium] › tests/cacheComponents.spec.ts:84:5 › Prerendered shell does not stitch the pageload onto a stale trace: ../../_temp/test-application/tests/cacheComponents.spec.ts#L97

7) [chromium] › tests/cacheComponents.spec.ts:84:5 › Prerendered shell does not stitch the pageload onto a stale trace Error: expect(locator).toHaveText(expected) failed Locator: locator('#todos-fetched') Expected: "Todos fetched: 5" Timeout: 10000ms Error: element(s) not found Call log: - Expect "toHaveText" locator('#todos-fetched') with timeout 10000ms - waiting for locator('#todos-fetched') 95 | await page.goto('/pageload-tracing'); 96 | > 97 | await expect(page.locator('#todos-fetched')).toHaveText('Todos fetched: 5'); | ^ 98 | 99 | const [serverTx, pageloadTx] = await Promise.all([serverTxPromise, pageloadTxPromise]); 100 | at /home/runner/work/_temp/test-application/tests/cacheComponents.spec.ts:97:48

[chromium] › tests/cacheComponents.spec.ts:71:5 › Should generate metadata async: ../../_temp/test-application/tests/cacheComponents.spec.ts#L80

6) [chromium] › tests/cacheComponents.spec.ts:71:5 › Should generate metadata async ────────────── Error: expect(locator).toHaveText(expected) failed Locator: locator('#todos-fetched') Expected: "Todos fetched: 5" Timeout: 10000ms Error: element(s) not found Call log: - Expect "toHaveText" locator('#todos-fetched') with timeout 10000ms - waiting for locator('#todos-fetched') 78 | 79 | expect(serverTx.spans?.filter(span => span.op === 'get.todos')).toHaveLength(0); > 80 | await expect(page.locator('#todos-fetched')).toHaveText('Todos fetched: 5'); | ^ 81 | await expect(page).toHaveTitle('Product: 1'); 82 | }); 83 | at /home/runner/work/_temp/test-application/tests/cacheComponents.spec.ts:80:48

[chromium] › tests/cacheComponents.spec.ts:58:5 › Should capture a message from an on-demand generated Server Component: ../../_temp/test-application/tests/cacheComponents.spec.ts#L65

5) [chromium] › tests/cacheComponents.spec.ts:58:5 › Should capture a message from an on-demand generated Server Component Error: expect(locator).toHaveText(expected) failed Locator: locator('#result') Expected: "Message captured for id message" Timeout: 10000ms Error: element(s) not found Call log: - Expect "toHaveText" locator('#result') with timeout 10000ms - waiting for locator('#result') 63 | await page.goto('/message'); 64 | > 65 | await expect(page.locator('#result')).toHaveText('Message captured for id message'); | ^ 66 | 67 | const message = await messagePromise; 68 | expect(message.message).toBe('Test message from cache components page'); at /home/runner/work/_temp/test-application/tests/cacheComponents.spec.ts:65:41

[chromium] › tests/cacheComponents.spec.ts:45:5 › Should capture an exception from an on-demand generated Server Component: ../../_temp/test-application/tests/cacheComponents.spec.ts#L52

4) [chromium] › tests/cacheComponents.spec.ts:45:5 › Should capture an exception from an on-demand generated Server Component Error: expect(locator).toHaveText(expected) failed Locator: locator('#result') Expected: "Error captured for id exception" Timeout: 10000ms Error: element(s) not found Call log: - Expect "toHaveText" locator('#result') with timeout 10000ms - waiting for locator('#result') 50 | await page.goto('/exception'); 51 | > 52 | await expect(page.locator('#result')).toHaveText('Error captured for id exception'); | ^ 53 | 54 | const error = await errorPromise; 55 | expect(error.exception?.values?.[0]?.value).toBe('Test error from cache components page'); at /home/runner/work/_temp/test-application/tests/cacheComponents.spec.ts:52:41

[chromium] › tests/cacheComponents.spec.ts:30:5 › Should generate metadata: ../../_temp/test-application/tests/cacheComponents.spec.ts#L39

3) [chromium] › tests/cacheComponents.spec.ts:30:5 › Should generate metadata ──────────────────── Error: expect(locator).toHaveText(expected) failed Locator: locator('#todos-fetched') Expected: "Todos fetched: 5" Timeout: 10000ms Error: element(s) not found Call log: - Expect "toHaveText" locator('#todos-fetched') with timeout 10000ms - waiting for locator('#todos-fetched') 37 | 38 | expect(serverTx.spans?.filter(span => span.op === 'get.todos')).toHaveLength(0); > 39 | await expect(page.locator('#todos-fetched')).toHaveText('Todos fetched: 5'); | ^ 40 | await expect(page).toHaveTitle('Cache Components Metadata Test'); 41 | }); 42 | at /home/runner/work/_temp/test-application/tests/cacheComponents.spec.ts:39:48

[chromium] › tests/cacheComponents.spec.ts:17:5 › Should render suspense component: ../../_temp/test-application/tests/cacheComponents.spec.ts#L26

2) [chromium] › tests/cacheComponents.spec.ts:17:5 › Should render suspense component ──────────── Error: expect(received).toBeGreaterThan(expected) Expected: > 0 Received: 0 24 | 25 | // this will be called several times in development mode, so we need to check for at least one span > 26 | expect(serverTx.spans?.filter(span => span.op === 'get.todos').length).toBeGreaterThan(0); | ^ 27 | await expect(page.locator('#todos-fetched')).toHaveText('Todos fetched: 5'); 28 | }); 29 | at /home/runner/work/_temp/test-application/tests/cacheComponents.spec.ts:26:74

[chromium] › tests/cacheComponents.spec.ts:4:5 › Should render cached component: ../../_temp/test-application/tests/cacheComponents.spec.ts#L14

1) [chromium] › tests/cacheComponents.spec.ts:4:5 › Should render cached component ─────────────── Error: expect(locator).toHaveText(expected) failed Locator: locator('#todos-fetched') Expected: "Todos fetched: 5" Timeout: 10000ms Error: element(s) not found Call log: - Expect "toHaveText" locator('#todos-fetched') with timeout 10000ms - waiting for locator('#todos-fetched') 12 | // we want to skip creating spans in cached environments 13 | expect(serverTx.spans?.filter(span => span.op === 'get.todos')).toHaveLength(0); > 14 | await expect(page.locator('#todos-fetched')).toHaveText('Todos fetched: 5'); | ^ 15 | }); 16 | 17 | test('Should render suspense component', async ({ page }) => { at /home/runner/work/_temp/test-application/tests/cacheComponents.spec.ts:14:48

🎭 Playwright Run Summary

1 failed [chromium] › tests/pi-durable.test.ts:23:1 › traces a run as invoke_agent with chat, execute_tool and provider spans 3 passed (12.3s)

🎭 Playwright Run Summary

1 failed [chromium] › tests/pi-durable.test.ts:21:5 › traces a PiHarness prompt as invoke_agent with chat, execute_tool and provider spans 2 passed (9.0s)

🎭 Playwright Run Summary

21 failed [chromium] › tests/cacheComponents.spec.ts:4:5 › Should render cached component ──────────────── [chromium] › tests/cacheComponents.spec.ts:17:5 › Should render suspense component ───────────── [chromium] › tests/cacheComponents.spec.ts:30:5 › Should generate metadata ───────────────────── [chromium] › tests/cacheComponents.spec.ts:45:5 › Should capture an exception from an on-demand generated Server Component [chromium] › tests/cacheComponents.spec.ts:58:5 › Should capture a message from an on-demand generated Server Component [chromium] › tests/cacheComponents.spec.ts:71:5 › Should generate metadata async ─────────────── [chromium] › tests/cacheComponents.spec.ts:84:5 › Prerendered shell does not stitch the pageload onto a stale trace [chromium] › tests/cacheComponents.spec.ts:116:5 › Should prerender a page that captures an exception in generateMetadata [chromium] › tests/cacheOriginLinks-nesting.spec.ts:11:5 › links a cached layout hit to the trace that filled the layout entry [chromium] › tests/cacheOriginLinks-nesting.spec.ts:55:5 › links a cached leaf component under dynamic layouts to the trace that filled the leaf entry [chromium] › tests/cacheOriginLinks-nesting.spec.ts:99:5 › links two cached levels to different origin traces after the layout expires [chromium] › tests/cacheOriginLinks-nesting.spec.ts:176:5 › links a shared layout hit on a sibling route to the trace of the route that filled the entry [chromium] › tests/cacheOriginLinks-page.spec.ts:13:5 › links each sibling component hit to the fill of its own entry [chromium] › tests/cacheOriginLinks-page.spec.ts:64:5 › links a nested cache hit inside another entry's refill to the original fill trace [chromium] › tests/cacheOriginLinks-routeHandler.spec.ts:8:5 › links a route handler cache hit to the trace that filled the entry [chromium] › tests/cacheOriginLinks-routeHandler.spec.ts:53:5 › moves the origin link to the refill trace after the entry expires [chromium] › tests/hangingPromiseRejection.spec.ts:13:5 › does not capture hanging prerender promise rejections on a runtime prefetch [chromium] › tests/prefetchOverlap.spec.ts:8:5 › overlapping runtime prefetch requests render their pages [chromium] › tests/useCacheSpans.spec.ts:4:5 › Should create cache spans around `use cache` functions [chromium] › tests/useCacheSpans.spec.ts:79:5 › Should create cache spans for `use cache` inside a rendered page [chromium] › tests/useCacheSpans.spec.ts:120:5 › Should report an expired entry as a miss and refill it 1 skipped 1 passed (6.6m)

Artifacts

Produced during runtime

Name	Size	Digest
E2E Test Dump (nextjs-16-cacheComponents (cloudflare))	6.57 KB	`sha256:78d2b7b3107646265b8d2c386ac0d14879a69c9832352791383eaa2faef57e2e`

Navigation Menu

Repository navigation

fix(nextjs): Don't abort Cache Components renders on Cloudflare Workers when requests overlap #61455

Summary

fix(nextjs): Don't abort Cache Components renders on Cloudflare Workers when requests overlap #61455

Uh oh!

build.yml

Annotations

Artifacts