Update Rspack production test manifest (#86233)

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

Author: vercel-release-bot

test/rspack-build-tests-manifest.json

@@ -101,6 +101,15 @@
     "flakey": [],
     "runtimeError": false
   },
+  "test/e2e/app-dir/actions-streaming/actions-streaming.test.ts": {
+    "passed": [
+      "actions-streaming actions returning a ReadableStream should properly stream the response without buffering"
+    ],
+    "failed": [],
+    "pending": [],
+    "flakey": [],
+    "runtimeError": false
+  },
   "test/e2e/app-dir/actions-unrecognized/actions-unrecognized.test.ts": {
     "passed": [
       "unrecognized server actions should 404 when POSTing a non-server-action request to a nonexistent page",
@@ -536,6 +545,7 @@
   },
   "test/e2e/app-dir/app-css/index.test.ts": {
     "passed": [
+      "app dir - css css support chunks should bundle css resources into chunks",
       "app dir - css css support client components should support css modules inside client components",
       "app dir - css css support client components should support css modules inside client page",
       "app dir - css css support client layouts should support css modules inside client layouts",
@@ -553,6 +563,7 @@
       "app dir - css css support special entries should include css imported in client not-found.js",
       "app dir - css css support special entries should include css imported in client template.js",
       "app dir - css css support special entries should include css imported in error.js",
+      "app dir - css css support special entries should include css imported in loading.js",
       "app dir - css css support special entries should include css imported in root not-found.js",
       "app dir - css css support special entries should include css imported in server not-found.js",
       "app dir - css css support special entries should include css imported in server template.js",
@@ -567,10 +578,7 @@
       "app dir - css sass support server pages should support global sass/scss inside server pages",
       "app dir - css sass support server pages should support sass/scss modules inside server pages"
     ],
-    "failed": [
-      "app dir - css css support chunks should bundle css resources into chunks",
-      "app dir - css css support special entries should include css imported in loading.js"
-    ],
+    "failed": [],
     "pending": [
       "app dir - css css support server layouts should support global css inside server layouts"
     ],
@@ -844,10 +852,11 @@
       "app dir - prefetching (custom staleTime) should fetch again when a static page was prefetched when navigating to it after the stale time has passed",
       "app dir - prefetching (custom staleTime) should fetch again when the initially visited static page is visited after the stale time has passed",
       "app dir - prefetching (custom staleTime) should not fetch again when a static page was prefetched when navigating to it twice",
-      "app dir - prefetching (custom staleTime) should not re-fetch cached data when navigating back to a route group",
       "app dir - prefetching (custom staleTime) should renew the stale time after refetching expired RSC data"
     ],
-    "failed": [],
+    "failed": [
+      "app dir - prefetching (custom staleTime) should not re-fetch cached data when navigating back to a route group"
+    ],
     "pending": [],
     "flakey": [],
     "runtimeError": false
@@ -3183,11 +3192,10 @@
   },
   "test/e2e/app-dir/initial-css-order/initial-css-order.test.ts": {
     "passed": [
+      "initial-css-order should serve styles in the correct order for global-not-found",
       "initial-css-order should serve styles in the correct order for the page"
     ],
-    "failed": [
-      "initial-css-order should serve styles in the correct order for global-not-found"
-    ],
+    "failed": [],
     "pending": [],
     "flakey": [],
     "runtimeError": false
@@ -3212,6 +3220,17 @@
   },
   "test/e2e/app-dir/interception-dynamic-segment/interception-dynamic-segment.test.ts": {
     "passed": [
+      "interception-dynamic-segment Default.tsx injection validation (no 404s allowed) should handle repeated interceptions without 404",
+      "interception-dynamic-segment Default.tsx injection validation (no 404s allowed) should navigate between different interception routes without 404",
+      "interception-dynamic-segment Default.tsx injection validation (no 404s allowed) should navigate to /explicit-layout/deeper without 404",
+      "interception-dynamic-segment Default.tsx injection validation (no 404s allowed) should navigate to /has-both without 404 (has both @sidebar and page)",
+      "interception-dynamic-segment Default.tsx injection validation (no 404s allowed) should navigate to /has-page without 404 (page fills children)",
+      "interception-dynamic-segment Default.tsx injection validation (no 404s allowed) should navigate to /no-parallel-routes/deeper without 404",
+      "interception-dynamic-segment Default.tsx injection validation (no 404s allowed) should navigate to /regular-route/deeper without 404 (has page)",
+      "interception-dynamic-segment Default.tsx injection validation (no 404s allowed) should navigate to /simple-page without 404 (no parallel routes)",
+      "interception-dynamic-segment Default.tsx injection validation (no 404s allowed) should navigate to /test-nested without 404 (auto null default)",
+      "interception-dynamic-segment Default.tsx injection validation (no 404s allowed) should navigate to /test-nested/deeper without 404",
+      "interception-dynamic-segment Default.tsx injection validation (no 404s allowed) should not render a 404 for the intercepted route with dynamic segments",
       "interception-dynamic-segment should correctly prerender segments with generateStaticParams",
       "interception-dynamic-segment should intercept consistently with back/forward navigation",
       "interception-dynamic-segment should intercept multiple times from root",
@@ -5917,7 +5936,7 @@
     "flakey": [],
     "runtimeError": false
   },
-  "test/e2e/app-dir/resume-data-cache/resume-data-cache/resume-data-cache.test.ts": {
+  "test/e2e/app-dir/resume-data-cache/resume-data-cache.test.ts": {
     "passed": [
       "resume-data-cache should have consistent data between static and dynamic renders with fetch cache",
       "resume-data-cache should have consistent data between static and dynamic renders with use cache"
@@ -6809,43 +6828,44 @@
   },
   "test/e2e/app-dir/segment-cache/prefetch-runtime/prefetch-runtime.test.ts": {
     "passed": [
+      "runtime prefetching cache stale time handling includes private caches with cacheLife(\"seconds\")",
+      "runtime prefetching cache stale time handling includes public caches with cacheLife(\"seconds\")",
+      "runtime prefetching cache stale time handling includes short-lived public caches with a long enough staleTime",
+      "runtime prefetching cache stale time handling omits private caches with a short enough staleTime",
+      "runtime prefetching cache stale time handling omits short-lived public caches with a short enough staleTime",
       "runtime prefetching can completely prefetch a page that is fully static",
+      "runtime prefetching errors aborts the prerender without logging an error when sync IO is used after awaiting a private cache",
+      "runtime prefetching errors aborts the prerender without logging an error when sync IO is used after awaiting a quickly-expiring public cache",
+      "runtime prefetching errors aborts the prerender without logging an error when sync IO is used after awaiting cookies()",
+      "runtime prefetching errors aborts the prerender without logging an error when sync IO is used after awaiting dynamic params",
+      "runtime prefetching errors aborts the prerender without logging an error when sync IO is used after awaiting headers()",
+      "runtime prefetching errors should trigger error boundaries for errors that occurred in runtime-prefetched content",
       "runtime prefetching in a page can completely prefetch a page that uses cookies and no uncached IO",
       "runtime prefetching in a page includes cookies, but not dynamic content",
       "runtime prefetching in a page includes dynamic params, but not dynamic content",
       "runtime prefetching in a page includes headers, but not dynamic content",
       "runtime prefetching in a page includes root params, but not dynamic content",
       "runtime prefetching in a page includes search params, but not dynamic content",
       "runtime prefetching in a private cache can completely prefetch a page that uses cookies and no uncached IO",
-      "runtime prefetching in a private cache includes cookies, but not dynamic content",
-      "runtime prefetching in a private cache includes dynamic params, but not dynamic content",
       "runtime prefetching in a private cache includes headers, but not dynamic content",
       "runtime prefetching in a private cache includes root params, but not dynamic content",
       "runtime prefetching in a private cache includes search params, but not dynamic content",
       "runtime prefetching passed to a public cache can completely prefetch a page that uses cookies and no uncached IO",
       "runtime prefetching passed to a public cache includes cookies, but not dynamic content",
-      "runtime prefetching passed to a public cache includes dynamic params, but not dynamic content",
-      "runtime prefetching passed to a public cache includes headers, but not dynamic content",
       "runtime prefetching passed to a public cache includes root params, but not dynamic content",
       "runtime prefetching passed to a public cache includes search params, but not dynamic content",
-      "runtime prefetching should not cache runtime prefetch responses in the browser cache or server-side different cookies should return different prefetch results - in a page",
       "runtime prefetching should not cache runtime prefetch responses in the browser cache or server-side different cookies should return different prefetch results - in a private cache",
       "runtime prefetching should not cache runtime prefetch responses in the browser cache or server-side private caches should return new results on each request"
     ],
-    "failed": [],
-    "pending": [
-      "runtime prefetching cache stale time handling includes private caches with cacheLife(\"seconds\")",
-      "runtime prefetching cache stale time handling includes public caches with cacheLife(\"seconds\")",
-      "runtime prefetching cache stale time handling includes short-lived public caches with a long enough staleTime",
-      "runtime prefetching cache stale time handling omits private caches with a short enough staleTime",
-      "runtime prefetching cache stale time handling omits short-lived public caches with a short enough staleTime",
-      "runtime prefetching errors aborts the prerender without logging an error when sync IO is used after awaiting a private cache",
-      "runtime prefetching errors aborts the prerender without logging an error when sync IO is used after awaiting a quickly-expiring public cache",
-      "runtime prefetching errors aborts the prerender without logging an error when sync IO is used after awaiting cookies()",
-      "runtime prefetching errors aborts the prerender without logging an error when sync IO is used after awaiting headers()",
+    "failed": [
       "runtime prefetching errors aborts the prerender without logging an error when sync IO is used after awaiting searchParams",
-      "runtime prefetching errors should trigger error boundaries for errors that occurred in runtime-prefetched content"
+      "runtime prefetching in a private cache includes cookies, but not dynamic content",
+      "runtime prefetching in a private cache includes dynamic params, but not dynamic content",
+      "runtime prefetching passed to a public cache includes dynamic params, but not dynamic content",
+      "runtime prefetching passed to a public cache includes headers, but not dynamic content",
+      "runtime prefetching should not cache runtime prefetch responses in the browser cache or server-side different cookies should return different prefetch results - in a page"
     ],
+    "pending": [],
     "flakey": [],
     "runtimeError": false
   },
@@ -7174,6 +7194,17 @@
     "flakey": [],
     "runtimeError": false
   },
+  "test/e2e/app-dir/transition-indicator/transition-indicator.test.ts": {
+    "passed": [
+      "transition-indicator displays during any Transition that does not commit a pending state",
+      "transition-indicator displays while loading content without fallback",
+      "transition-indicator does not display while loading content with fallback"
+    ],
+    "failed": [],
+    "pending": [],
+    "flakey": [],
+    "runtimeError": false
+  },
   "test/e2e/app-dir/turbopack-reports/turbopack-reports.test.ts": {
     "passed": ["turbopack-reports should render page importing sqlite3"],
     "failed": [],
@@ -9875,6 +9906,7 @@
       "opentelemetry root context pages should handle getServerSideProps on edge",
       "opentelemetry root context pages should handle getServerSideProps returning notFound",
       "opentelemetry root context pages should handle getStaticProps when fallback: 'blocking'",
+      "opentelemetry with custom server should set attributes correctly on handleRequest span",
       "opentelemetry with disabled fetch tracing root context app router with disabled fetch should handle RSC with disabled fetch"
     ],
     "failed": [],
@@ -11160,11 +11192,11 @@
     "runtimeError": false
   },
   "test/integration/app-document-remove-hmr/test/index.test.ts": {
-    "passed": [],
-    "failed": [
+    "passed": [
       "_app removal HMR should HMR when _app is removed",
       "_app removal HMR should HMR when _document is removed"
     ],
+    "failed": [],
     "pending": [],
     "flakey": [],
     "runtimeError": false
@@ -11400,16 +11432,6 @@
     "flakey": [],
     "runtimeError": false
   },
-  "test/integration/clean-distdir/test/index.test.ts": {
-    "passed": [],
-    "failed": [
-      "Cleaning distDir production mode disabled write should not clean up .next before build start",
-      "Cleaning distDir production mode should clean up .next before build start"
-    ],
-    "pending": [],
-    "flakey": [],
-    "runtimeError": false
-  },
   "test/integration/cli/test/index.test.ts": {
     "passed": [
       "CLI Usage dev --experimental-https",
@@ -20376,6 +20398,15 @@
     "flakey": [],
     "runtimeError": false
   },
+  "test/production/app-dir/actions/app-action-body-finalize-output-standalone.test.ts": {
+    "passed": [
+      "app-dir action body finalize with nodejs middleware and output-standalone should handle large payload through server action after nodejs middleware with delayed body finalize"
+    ],
+    "failed": [],
+    "pending": [],
+    "flakey": [],
+    "runtimeError": false
+  },
   "test/production/app-dir/app-edge-middleware/app-edge-middleware.test.ts": {
     "passed": [
       "app edge middleware with node.js modules should have errors about using Node.js modules when present in middleware",
@@ -20444,7 +20475,8 @@
   "test/production/app-dir/browser-chunks/browser-chunks.test.ts": {
     "passed": [
       "browser-chunks must not bundle any dev overlay into browser chunks",
-      "browser-chunks must not bundle any server modules into browser chunks"
+      "browser-chunks must not bundle any server modules into browser chunks",
+      "browser-chunks must not include heavy dependencies into browser chunks"
     ],
     "failed": [],
     "pending": [],
@@ -20463,11 +20495,11 @@
       "build-output-prerender with a next config file with --debug-prerender prints a warning and the customized experimental flags",
       "build-output-prerender with a next config file with --debug-prerender shows all prerender errors with readable stacks and code frames",
       "build-output-prerender with a next config file without --debug-prerender shows only a single prerender error with a mangled stack",
-      "build-output-prerender without a next config file with --debug-prerender prints a warning and the customized experimental flags",
       "build-output-prerender without a next config file without --debug-prerender prints no experimental flags (unless enabled via env variable)"
     ],
     "failed": [
-      "build-output-prerender with a next config file without --debug-prerender prints only the user-selected experimental flags (and the ones enabled via env variable)"
+      "build-output-prerender with a next config file without --debug-prerender prints only the user-selected experimental flags (and the ones enabled via env variable)",
+      "build-output-prerender without a next config file with --debug-prerender prints a warning and the customized experimental flags"
     ],
     "pending": [],
     "flakey": [],
@@ -20587,6 +20619,15 @@
     "flakey": [],
     "runtimeError": false
   },
+  "test/production/app-dir/metadata-base-warning/metadata-base-warning.test.ts": {
+    "passed": [
+      "metadata-base-warning should not warn metadataBase for static image when metadataBase is set"
+    ],
+    "failed": [],
+    "pending": [],
+    "flakey": [],
+    "runtimeError": false
+  },
   "test/production/app-dir/metadata-img-too-large/opengraph-image/index.test.ts": {
     "passed": [
       "app-dir - metadata-img-too-large opengraph-image should throw when opengraph-image file size exceeds 8MB"
@@ -20864,6 +20905,17 @@
     "flakey": [],
     "runtimeError": false
   },
+  "test/production/app-type/app-type.test.ts": {
+    "passed": [
+      "app-type app-only should have the app-only app type",
+      "app-type hybrid should have the hybrid app type",
+      "app-type pages-only should have the pages-only app type"
+    ],
+    "failed": [],
+    "pending": [],
+    "flakey": [],
+    "runtimeError": false
+  },
   "test/production/bfcache-routing/index.test.ts": {
     "passed": [],
     "failed": [],
@@ -20919,6 +20971,16 @@
     "flakey": [],
     "runtimeError": false
   },
+  "test/production/clean-distdir/index.test.ts": {
+    "passed": [
+      "Cleaning distDir disabled write should clean up .next before build start",
+      "Cleaning distDir disabled write should not clean up .next before build start"
+    ],
+    "failed": [],
+    "pending": [],
+    "flakey": [],
+    "runtimeError": false
+  },
   "test/production/config-validation-fatal-errors/index.test.ts": {
     "passed": [
       "config validation - fatal errors should show warnings first, then throw fatal error"