Update Turbopack production test manifest #74780

vercel-release-bot · 2025-01-11T07:04:34Z

This auto-generated PR updates the production integration test manifest used when testing Turbopack.

ijjk · 2025-01-11T07:14:54Z

Failing test suites

Commit: 0a895f8

pnpm test test/integration/app-dir-export/test/dynamicapiroute-prod.test.ts (turbopack)

app dir - with output export - dynamic api route prod > production mode > should work in prod with dynamicApiRoute 'error'
app dir - with output export - dynamic api route prod > production mode > should work in prod with dynamicApiRoute 'force-static'
app dir - with output export - dynamic api route prod > production mode > should work in prod with dynamicApiRoute 'force-dynamic'

Expand output

● app dir - with output export - dynamic api route prod › production mode › should work in prod with dynamicApiRoute 'error'

thrown: "Exceeded timeout of 60000 ms for a test.
Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout."

  18 |             'export const dynamic = "force-dynamic" on page "/api/json" cannot be used with "output: export".',
  19 |         },
> 20 |       ])(
     |        ^
  21 |         'should work in prod with dynamicApiRoute $dynamicApiRoute',
  22 |         async ({ dynamicApiRoute, expectedErrMsg }) => {
  23 |           await runTests({ isDev: false, dynamicApiRoute, expectedErrMsg })

  at ../node_modules/.pnpm/[email protected]/node_modules/jest-each/build/bind.js:47:15
      at Array.forEach (<anonymous>)
  at integration/app-dir-export/test/dynamicapiroute-prod.test.ts:20:8
  at integration/app-dir-export/test/dynamicapiroute-prod.test.ts:4:56
  at Object.describe (integration/app-dir-export/test/dynamicapiroute-prod.test.ts:3:1)

● app dir - with output export - dynamic api route prod › production mode › should work in prod with dynamicApiRoute 'force-static'

Failed to replace content.

Pattern: const dynamic = 'force-static'

Content: export const dynamic = 'error'

export async function GET() {
  return Response.json({ answer: 42 })
}

  764 |     } else if (typeof pattern === 'string') {
  765 |       if (!currentContent.includes(pattern)) {
> 766 |         throw new Error(
      |               ^
  767 |           `Failed to replace content.\n\nPattern: ${pattern}\n\nContent: ${currentContent}`
  768 |         )
  769 |       }

  at File.replace (lib/next-test-utils.ts:766:15)
  at replace (integration/app-dir-export/test/utils.ts:136:13)
  at integration/app-dir-export/test/dynamicapiroute-prod.test.ts:23:25

● app dir - with output export - dynamic api route prod › production mode › should work in prod with dynamicApiRoute 'force-dynamic'

Failed to replace content.

Pattern: const dynamic = 'force-static'

Content: export const dynamic = 'error'

export async function GET() {
  return Response.json({ answer: 42 })
}

  764 |     } else if (typeof pattern === 'string') {
  765 |       if (!currentContent.includes(pattern)) {
> 766 |         throw new Error(
      |               ^
  767 |           `Failed to replace content.\n\nPattern: ${pattern}\n\nContent: ${currentContent}`
  768 |         )
  769 |       }

  at File.replace (lib/next-test-utils.ts:766:15)
  at replace (integration/app-dir-export/test/utils.ts:136:13)
  at integration/app-dir-export/test/dynamicapiroute-prod.test.ts:23:25

Read more about building and testing Next.js in contributing.md.

pnpm test-dev test/e2e/app-dir/actions/app-action.test.ts

app-dir action handling > should forward action request to a worker that contains the action handler (node)
app-dir action handling > should forward action request to a worker that contains the action handler (edge)
app-dir action handling > should not error when a forwarded action triggers a redirect (node)
app-dir action handling > should work with interception routes
app-dir action handling > fetch actions > should handle redirects to routes that provide an invalid RSC response

Expand output

● app-dir action handling › should forward action request to a worker that contains the action handler (node)

page.waitForSelector: Timeout 60000ms exceeded.
Call log:
  - waiting for locator('#other-page')

  423 |     return this.chain(() => {
  424 |       return page
> 425 |         .waitForSelector(selector, { timeout, state: 'attached' })
      |          ^
  426 |         .then(async (el) => {
  427 |           // it seems selenium waits longer and tests rely on this behavior
  428 |           // so we wait for the load event fire before returning

  at waitForSelector (lib/browsers/playwright.ts:425:10)
  at e2e/app-dir/actions/app-action.test.ts:862:7
  at Proxy.chain (lib/browsers/base.ts:17:23)
  at Proxy.chain (lib/browsers/playwright.ts:423:17)
  at waitForElementByCss (e2e/app-dir/actions/app-action.test.ts:865:10)

● app-dir action handling › should forward action request to a worker that contains the action handler (edge)

page.waitForSelector: Timeout 60000ms exceeded.
Call log:
  - waiting for locator('#other-page')

  423 |     return this.chain(() => {
  424 |       return page
> 425 |         .waitForSelector(selector, { timeout, state: 'attached' })
      |          ^
  426 |         .then(async (el) => {
  427 |           // it seems selenium waits longer and tests rely on this behavior
  428 |           // so we wait for the load event fire before returning

  at waitForSelector (lib/browsers/playwright.ts:425:10)
  at e2e/app-dir/actions/app-action.test.ts:862:7
  at Proxy.chain (lib/browsers/base.ts:17:23)
  at Proxy.chain (lib/browsers/playwright.ts:423:17)
  at waitForElementByCss (e2e/app-dir/actions/app-action.test.ts:865:10)

● app-dir action handling › should not error when a forwarded action triggers a redirect (node)

page.waitForSelector: Timeout 60000ms exceeded.
Call log:
  - waiting for locator('#other-page')

  423 |     return this.chain(() => {
  424 |       return page
> 425 |         .waitForSelector(selector, { timeout, state: 'attached' })
      |          ^
  426 |         .then(async (el) => {
  427 |           // it seems selenium waits longer and tests rely on this behavior
  428 |           // so we wait for the load event fire before returning

  at waitForSelector (lib/browsers/playwright.ts:425:10)
  at e2e/app-dir/actions/app-action.test.ts:905:7
  at Proxy.chain (lib/browsers/base.ts:17:23)
  at Proxy.chain (lib/browsers/playwright.ts:423:17)
  at waitForElementByCss (e2e/app-dir/actions/app-action.test.ts:908:10)

● app-dir action handling › fetch actions › should handle redirects to routes that provide an invalid RSC response

expect(received).toContain(expected) // indexOf

Expected substring: "Hello from a pages route"
Received string:    "0.05323038765813992
Client
Server
Client and Server
0
+1+1 (Slow)-1*2
redirect to a pages route
submit
test"

  1269 |
  1270 |       await retry(async () => {
> 1271 |         expect(await browser.elementByCss('body').text()).toContain(
       |                                                           ^
  1272 |           'Hello from a pages route'
  1273 |         )
  1274 |         expect(await browser.url()).toBe(`${next.url}/pages-dir`)

  at toContain (e2e/app-dir/actions/app-action.test.ts:1271:59)
  at retry (lib/next-test-utils.ts:806:14)
  at Object.<anonymous> (e2e/app-dir/actions/app-action.test.ts:1270:7)

● app-dir action handling › should work with interception routes

expect(received).toContain(expected) // indexOf

Expected substring: "interception-routes/test"
Received string:    "http://localhost:34355/interception-routes"

  1544 |     await retry(async () => {
  1545 |       // verify the URL is correct
> 1546 |       expect(await browser.url()).toContain('interception-routes/test')
       |                                   ^
  1547 |       // the intercepted text should appear
  1548 |       expect(await browser.elementById('modal-data').text()).toContain(
  1549 |         'in "modal"'

  at toContain (e2e/app-dir/actions/app-action.test.ts:1546:35)
  at retry (lib/next-test-utils.ts:806:14)
  at Object.<anonymous> (e2e/app-dir/actions/app-action.test.ts:1544:5)

Read more about building and testing Next.js in contributing.md.

ijjk · 2025-01-11T07:21:26Z

Stats from current PR

Default Build (Increase detected ⚠️)

General

	vercel/next.js canary	vercel/next.js update/turbopack-manifest-1736579067940	Change
buildDuration	49.1s	48.1s	N/A
buildDurationCached	48.6s	40.8s	N/A
nodeModulesSize	417 MB	417 MB	✓
nextStartRea..uration (ms)	1.2s	1.3s	N/A

Client Bundles (main, webpack)

	vercel/next.js canary	vercel/next.js update/turbopack-manifest-1736579067940	Change
5306-HASH.js gzip	53.3 kB	53.3 kB	N/A
8276.HASH.js gzip	169 B	168 B	N/A
8377-HASH.js gzip	5.44 kB	5.44 kB	N/A
bccd1874-HASH.js gzip	53 kB	53 kB	✓
framework-HASH.js gzip	57.5 kB	57.5 kB	N/A
main-app-HASH.js gzip	240 B	242 B	N/A
main-HASH.js gzip	34.2 kB	34.2 kB	N/A
webpack-HASH.js gzip	1.71 kB	1.71 kB	N/A
Overall change	53 kB	53 kB	✓

Legacy Client Bundles (polyfills)

	vercel/next.js canary	vercel/next.js update/turbopack-manifest-1736579067940	Change
polyfills-HASH.js gzip	39.4 kB	39.4 kB	✓
Overall change	39.4 kB	39.4 kB	✓

Client Pages

	vercel/next.js canary	vercel/next.js update/turbopack-manifest-1736579067940	Change
_app-HASH.js gzip	193 B	193 B	✓
_error-HASH.js gzip	193 B	193 B	✓
amp-HASH.js gzip	512 B	510 B	N/A
css-HASH.js gzip	343 B	342 B	N/A
dynamic-HASH.js gzip	1.84 kB	1.84 kB	✓
edge-ssr-HASH.js gzip	265 B	265 B	✓
head-HASH.js gzip	363 B	362 B	N/A
hooks-HASH.js gzip	393 B	392 B	N/A
image-HASH.js gzip	4.57 kB	4.57 kB	N/A
index-HASH.js gzip	268 B	268 B	✓
link-HASH.js gzip	2.35 kB	2.34 kB	N/A
routerDirect..HASH.js gzip	328 B	328 B	✓
script-HASH.js gzip	397 B	397 B	✓
withRouter-HASH.js gzip	323 B	326 B	N/A
1afbb74e6ecf..834.css gzip	106 B	106 B	✓
Overall change	3.59 kB	3.59 kB	✓

Client Build Manifests

	vercel/next.js canary	vercel/next.js update/turbopack-manifest-1736579067940	Change
_buildManifest.js gzip	749 B	747 B	N/A
Overall change	0 B	0 B	✓

Rendered Page Sizes

	vercel/next.js canary	vercel/next.js update/turbopack-manifest-1736579067940	Change
index.html gzip	523 B	524 B	N/A
link.html gzip	537 B	538 B	N/A
withRouter.html gzip	518 B	520 B	N/A
Overall change	0 B	0 B	✓

Edge SSR bundle Size

	vercel/next.js canary	vercel/next.js update/turbopack-manifest-1736579067940	Change
edge-ssr.js gzip	129 kB	129 kB	N/A
page.js gzip	207 kB	207 kB	N/A
Overall change	0 B	0 B	✓

Middleware size

	vercel/next.js canary	vercel/next.js update/turbopack-manifest-1736579067940	Change
middleware-b..fest.js gzip	670 B	668 B	N/A
middleware-r..fest.js gzip	155 B	156 B	N/A
middleware.js gzip	31.2 kB	31.2 kB	N/A
edge-runtime..pack.js gzip	844 B	844 B	✓
Overall change	844 B	844 B	✓

Next Runtimes

	vercel/next.js canary	vercel/next.js update/turbopack-manifest-1736579067940	Change
274-experime...dev.js gzip	322 B	322 B	✓
274.runtime.dev.js gzip	314 B	314 B	✓
app-page-exp...dev.js gzip	369 kB	369 kB	✓
app-page-exp..prod.js gzip	130 kB	130 kB	✓
app-page-tur..prod.js gzip	142 kB	142 kB	✓
app-page-tur..prod.js gzip	138 kB	138 kB	✓
app-page.run...dev.js gzip	357 kB	357 kB	✓
app-page.run..prod.js gzip	126 kB	126 kB	✓
app-route-ex...dev.js gzip	37.6 kB	37.6 kB	✓
app-route-ex..prod.js gzip	25.6 kB	25.6 kB	✓
app-route-tu..prod.js gzip	25.6 kB	25.6 kB	✓
app-route-tu..prod.js gzip	25.4 kB	25.4 kB	✓
app-route.ru...dev.js gzip	39.2 kB	39.2 kB	✓
app-route.ru..prod.js gzip	25.4 kB	25.4 kB	✓
pages-api-tu..prod.js gzip	9.69 kB	9.69 kB	✓
pages-api.ru...dev.js gzip	11.6 kB	11.6 kB	✓
pages-api.ru..prod.js gzip	9.68 kB	9.68 kB	✓
pages-turbo...prod.js gzip	21.7 kB	21.7 kB	✓
pages.runtim...dev.js gzip	27.5 kB	27.5 kB	✓
pages.runtim..prod.js gzip	21.7 kB	21.7 kB	✓
server.runti..prod.js gzip	916 kB	916 kB	✓
Overall change	2.46 MB	2.46 MB	✓

build cache Overall increase ⚠️

	vercel/next.js canary	vercel/next.js update/turbopack-manifest-1736579067940	Change
0.pack gzip	2.09 MB	2.09 MB	⚠️ +453 B
index.pack gzip	74.1 kB	75.4 kB	⚠️ +1.23 kB
Overall change	2.17 MB	2.17 MB	⚠️ +1.69 kB

Diff details

Diff for main-HASH.js

Diff too large to display

Commit: 0a895f8

update/turbopack-manifest-1736579067940

0a895f8

ijjk added CI approved Approve running CI for fork tests labels Jan 11, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update Turbopack production test manifest #74780

Update Turbopack production test manifest #74780

vercel-release-bot commented Jan 11, 2025

ijjk commented Jan 11, 2025 •

edited

Loading

ijjk commented Jan 11, 2025

Update Turbopack production test manifest #74780

Are you sure you want to change the base?

Update Turbopack production test manifest #74780

Conversation

vercel-release-bot commented Jan 11, 2025

ijjk commented Jan 11, 2025 • edited Loading

Failing test suites

ijjk commented Jan 11, 2025

Stats from current PR

ijjk commented Jan 11, 2025 •

edited

Loading