Skip to content

Upload Next.js server logs as artifact for Windows E2E#946

Merged
TooTallNate merged 1 commit intomainfrom
02-04-upload_next.js_server_logs_as_artifact_for_windows_e2e
Feb 5, 2026
Merged

Upload Next.js server logs as artifact for Windows E2E#946
TooTallNate merged 1 commit intomainfrom
02-04-upload_next.js_server_logs_as_artifact_for_windows_e2e

Conversation

@TooTallNate
Copy link
Copy Markdown
Member

@TooTallNate TooTallNate commented Feb 5, 2026 •
edited
Loading

Improved Next.js E2E test debugging on Windows by capturing and exposing server logs.

What changed?

  • Modified the Windows E2E test workflow to capture Next.js server logs during test execution
  • Added a step to print the server logs to the GitHub Actions console after tests complete
  • Added an artifact upload step to preserve the Next.js server logs for later inspection

How to test?

Run the E2E tests on Windows and verify that:

  1. The Next.js server logs are properly captured to nextjs-server.log
  2. The logs are printed to the console after test completion
  3. The logs are uploaded as an artifact named nextjs-server-logs-windows

Why make this change?

This change enhances debugging capabilities for Next.js E2E tests on Windows. By capturing, displaying, and preserving the server logs, it becomes much easier to diagnose test failures that might be related to server-side issues, which were previously invisible in the test output.

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Feb 5, 2026

🦋 Changeset detected

Latest commit: df5a8b3

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 0 packages

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Feb 5, 2026 •
edited
Loading

🧪 E2E Test Results

❌ Some tests failed

Summary

Passed Failed Skipped Total
✅ ▲ Vercel Production 479 0 38 517
✅ 💻 Local Development 438 0 32 470
✅ 📦 Local Production 438 0 32 470
✅ 🐘 Local Postgres 438 0 32 470
✅ 🪟 Windows 47 0 0 47
❌ 🌍 Community Worlds 31 169 0 200
✅ 📋 Other 129 0 12 141
Total 2000 169 146 2315

❌ Failed Tests

🌍 Community Worlds (169 failed)

mongodb (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • error handling error propagation workflow errors nested function calls preserve message and stack trace
  • error handling error propagation workflow errors cross-file imports preserve message and stack trace
  • error handling error propagation step errors basic step error preserves message and stack trace
  • error handling error propagation step errors cross-file step error preserves message and function names in stack
  • error handling retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

redis (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • error handling error propagation workflow errors nested function calls preserve message and stack trace
  • error handling error propagation workflow errors cross-file imports preserve message and stack trace
  • error handling error propagation step errors basic step error preserves message and stack trace
  • error handling error propagation step errors cross-file step error preserves message and function names in stack
  • error handling retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

starter (43 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • error handling error propagation workflow errors nested function calls preserve message and stack trace
  • error handling error propagation workflow errors cross-file imports preserve message and stack trace
  • error handling error propagation step errors basic step error preserves message and stack trace
  • error handling error propagation step errors cross-file step error preserves message and function names in stack
  • error handling retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • health check (CLI) - workflow health command reports healthy endpoints
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

turso (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • error handling error propagation workflow errors nested function calls preserve message and stack trace
  • error handling error propagation workflow errors cross-file imports preserve message and stack trace
  • error handling error propagation step errors basic step error preserves message and stack trace
  • error handling error propagation step errors cross-file step error preserves message and function names in stack
  • error handling retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

Details by Category

✅ ▲ Vercel Production
App Passed Failed Skipped
✅ astro 43 0 4
✅ example 43 0 4
✅ express 43 0 4
✅ fastify 43 0 4
✅ hono 43 0 4
✅ nextjs-turbopack 46 0 1
✅ nextjs-webpack 46 0 1
✅ nitro 43 0 4
✅ nuxt 43 0 4
✅ sveltekit 43 0 4
✅ vite 43 0 4
✅ 💻 Local Development
App Passed Failed Skipped
✅ astro-stable 43 0 4
✅ express-stable 43 0 4
✅ fastify-stable 43 0 4
✅ hono-stable 43 0 4
✅ nextjs-turbopack-stable 47 0 0
✅ nextjs-webpack-stable 47 0 0
✅ nitro-stable 43 0 4
✅ nuxt-stable 43 0 4
✅ sveltekit-stable 43 0 4
✅ vite-stable 43 0 4
✅ 📦 Local Production
App Passed Failed Skipped
✅ astro-stable 43 0 4
✅ express-stable 43 0 4
✅ fastify-stable 43 0 4
✅ hono-stable 43 0 4
✅ nextjs-turbopack-stable 47 0 0
✅ nextjs-webpack-stable 47 0 0
✅ nitro-stable 43 0 4
✅ nuxt-stable 43 0 4
✅ sveltekit-stable 43 0 4
✅ vite-stable 43 0 4
✅ 🐘 Local Postgres
App Passed Failed Skipped
✅ astro-stable 43 0 4
✅ express-stable 43 0 4
✅ fastify-stable 43 0 4
✅ hono-stable 43 0 4
✅ nextjs-turbopack-stable 47 0 0
✅ nextjs-webpack-stable 47 0 0
✅ nitro-stable 43 0 4
✅ nuxt-stable 43 0 4
✅ sveltekit-stable 43 0 4
✅ vite-stable 43 0 4
✅ 🪟 Windows
App Passed Failed Skipped
✅ nextjs-turbopack 47 0 0
❌ 🌍 Community Worlds
App Passed Failed Skipped
✅ mongodb-dev 3 0 0
❌ mongodb 5 42 0
✅ redis-dev 3 0 0
❌ redis 5 42 0
✅ starter-dev 3 0 0
❌ starter 4 43 0
✅ turso-dev 3 0 0
❌ turso 5 42 0
✅ 📋 Other
App Passed Failed Skipped
✅ e2e-local-dev-nest-stable 43 0 4
✅ e2e-local-postgres-nest-stable 43 0 4
✅ e2e-local-prod-nest-stable 43 0 4

📋 View full workflow run

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Feb 5, 2026 •
edited
Loading

📊 Benchmark Results

📈 Comparing against baseline from main branch. Green 🟢 = faster, Red 🔺 = slower.

workflow with no steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 0.037s (-1.6%) 1.016s (~) 0.978s 10 1.00x
💻 Local Express 0.042s (-4.3%) 1.007s (~) 0.965s 10 1.13x
💻 Local Nitro 0.044s (+52.8% 🔺) 1.008s (~) 0.964s 10 1.17x
🐘 Postgres Nitro 0.197s (-42.5% 🟢) 1.014s (~) 0.816s 10 5.26x
🐘 Postgres Express 0.203s (-13.9% 🟢) 1.016s (~) 0.812s 10 5.43x
🐘 Postgres Next.js (Turbopack) 0.367s (+9.2% 🔺) 1.025s (-0.8%) 0.657s 10 9.80x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 0.647s (-11.6% 🟢) 1.516s (-13.0% 🟢) 0.869s 10 1.00x
▲ Vercel Next.js (Turbopack) 0.667s (-2.6%) 1.618s (+5.6% 🔺) 0.951s 10 1.03x
▲ Vercel Express 0.751s (+14.8% 🔺) 1.837s (+23.7% 🔺) 1.085s 10 1.16x

🔍 Observability: Nitro | Next.js (Turbopack) | Express

workflow with 1 step

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 1.099s (~) 2.012s (~) 0.913s 10 1.00x
💻 Local Express 1.112s (-0.7%) 2.007s (~) 0.895s 10 1.01x
💻 Local Nitro 1.115s (+3.3%) 2.008s (~) 0.893s 10 1.01x
🐘 Postgres Next.js (Turbopack) 1.733s (-15.4% 🟢) 2.015s (-28.6% 🟢) 0.282s 10 1.58x
🐘 Postgres Nitro 2.300s (-3.1%) 3.014s (~) 0.713s 10 2.09x
🐘 Postgres Express 2.333s (+4.9%) 3.015s (~) 0.682s 10 2.12x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.795s (-3.1%) 3.934s (+7.4% 🔺) 1.138s 10 1.00x
▲ Vercel Nitro 2.812s (-9.8% 🟢) 3.644s (-7.9% 🟢) 0.832s 10 1.01x
▲ Vercel Next.js (Turbopack) 3.370s (+16.4% 🔺) 4.063s (+11.0% 🔺) 0.693s 10 1.21x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

workflow with 10 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 10.706s (~) 11.020s (~) 0.314s 3 1.00x
💻 Local Nitro 10.814s (+2.4%) 11.014s (~) 0.200s 3 1.01x
💻 Local Express 10.817s (~) 11.015s (~) 0.198s 3 1.01x
🐘 Postgres Next.js (Turbopack) 15.122s (~) 16.031s (+3.2%) 0.909s 2 1.41x
🐘 Postgres Express 20.424s (~) 21.039s (~) 0.616s 2 1.91x
🐘 Postgres Nitro 20.460s (+1.1%) 21.027s (~) 0.566s 2 1.91x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 22.614s (-3.1%) 23.427s (-3.6%) 0.813s 2 1.00x
▲ Vercel Express 23.232s (+2.4%) 24.135s (+4.6%) 0.903s 2 1.03x
▲ Vercel Next.js (Turbopack) 23.566s (~) 24.601s (+2.5%) 1.035s 2 1.04x

🔍 Observability: Nitro | Express | Next.js (Turbopack)

workflow with 25 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 27.208s (~) 28.031s (~) 0.823s 3 1.00x
💻 Local Express 27.414s (-0.6%) 28.022s (~) 0.608s 3 1.01x
💻 Local Nitro 27.453s (+2.5%) 28.029s (+3.7%) 0.576s 3 1.01x
🐘 Postgres Next.js (Turbopack) 36.798s (-1.4%) 37.551s (-1.4%) 0.753s 2 1.35x
🐘 Postgres Express 50.290s (~) 51.085s (~) 0.795s 2 1.85x
🐘 Postgres Nitro 50.376s (+1.1%) 51.077s (+1.0%) 0.701s 2 1.85x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 56.674s (-2.0%) 57.634s (-1.1%) 0.960s 2 1.00x
▲ Vercel Nitro 57.022s (-1.7%) 57.486s (-2.4%) 0.464s 2 1.01x
▲ Vercel Express 57.373s (~) 58.303s (~) 0.930s 2 1.01x

🔍 Observability: Next.js (Turbopack) | Nitro | Express

workflow with 50 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 56.587s (~) 57.041s (~) 0.453s 2 1.00x
💻 Local Express 57.050s (-0.6%) 57.549s (-0.9%) 0.499s 2 1.01x
💻 Local Nitro 57.215s (+2.8%) 58.026s (+3.5%) 0.812s 2 1.01x
🐘 Postgres Next.js (Turbopack) 67.376s (-10.5% 🟢) 68.102s (-10.5% 🟢) 0.725s 2 1.19x
🐘 Postgres Nitro 100.196s (~) 101.154s (~) 0.958s 1 1.77x
🐘 Postgres Express 100.595s (~) 101.115s (~) 0.520s 1 1.78x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 119.686s (-4.1%) 120.507s (-3.6%) 0.821s 1 1.00x
▲ Vercel Next.js (Turbopack) 121.393s (~) 121.919s (-0.7%) 0.526s 1 1.01x
▲ Vercel Express 121.885s (+2.2%) 122.433s (+1.8%) 0.548s 1 1.02x

🔍 Observability: Nitro | Next.js (Turbopack) | Express

Promise.all with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Express 1.397s (-2.3%) 2.006s (~) 0.610s 15 1.00x
💻 Local Next.js (Turbopack) 1.411s (+2.7%) 2.012s (~) 0.600s 15 1.01x
💻 Local Nitro 1.411s (+4.2%) 2.006s (~) 0.594s 15 1.01x
🐘 Postgres Next.js (Turbopack) 2.231s (-4.8%) 2.761s (+2.1%) 0.530s 11 1.60x
🐘 Postgres Express 2.265s (~) 3.013s (~) 0.748s 10 1.62x
🐘 Postgres Nitro 2.335s (-6.5% 🟢) 3.011s (~) 0.676s 10 1.67x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.877s (~) 3.869s (+2.2%) 0.992s 8 1.00x
▲ Vercel Next.js (Turbopack) 2.932s (-9.3% 🟢) 3.882s (-5.2% 🟢) 0.950s 8 1.02x
▲ Vercel Nitro 3.049s (+2.9%) 3.896s (-0.9%) 0.847s 8 1.06x

🔍 Observability: Express | Next.js (Turbopack) | Nitro

Promise.all with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 2.500s (+1.4%) 3.051s (~) 0.550s 10 1.00x
💻 Local Express 2.541s (-4.0%) 3.015s (~) 0.474s 10 1.02x
💻 Local Nitro 2.577s (+15.2% 🔺) 3.017s (-6.2% 🟢) 0.440s 10 1.03x
🐘 Postgres Nitro 8.324s (-0.9%) 9.068s (~) 0.744s 4 3.33x
🐘 Postgres Express 9.085s (+2.9%) 9.822s (+5.5% 🔺) 0.737s 4 3.63x
🐘 Postgres Next.js (Turbopack) 13.004s (-3.8%) 13.371s (-4.7%) 0.367s 3 5.20x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 3.376s (-6.2% 🟢) 4.546s (+5.6% 🔺) 1.170s 7 1.00x
▲ Vercel Nitro 3.405s (-5.6% 🟢) 4.119s (-21.8% 🟢) 0.713s 8 1.01x
▲ Vercel Express 3.496s (+15.0% 🔺) 4.250s (+11.8% 🔺) 0.754s 8 1.04x

🔍 Observability: Next.js (Turbopack) | Nitro | Express

Promise.all with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Express 7.093s (-9.2% 🟢) 7.395s (-15.2% 🟢) 0.302s 5 1.00x
💻 Local Next.js (Turbopack) 7.136s (+10.2% 🔺) 7.782s (+8.7% 🔺) 0.646s 5 1.01x
💻 Local Nitro 7.470s (+22.1% 🔺) 8.454s (+25.4% 🔺) 0.984s 4 1.05x
🐘 Postgres Nitro 44.071s (-13.9% 🟢) 44.455s (-14.7% 🟢) 0.384s 1 6.21x
🐘 Postgres Express 44.229s (-7.4% 🟢) 45.162s (-6.5% 🟢) 0.933s 1 6.24x
🐘 Postgres Next.js (Turbopack) 53.051s (-4.5%) 53.146s (-5.6% 🟢) 0.095s 1 7.48x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 3.381s (-2.1%) 4.791s (+17.1% 🔺) 1.409s 7 1.00x
▲ Vercel Nitro 4.208s (+20.5% 🔺) 4.728s (+14.8% 🔺) 0.520s 7 1.24x
▲ Vercel Next.js (Turbopack) 4.676s (+25.3% 🔺) 5.505s (+23.5% 🔺) 0.829s 6 1.38x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

Promise.race with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Nitro 1.411s (+3.9%) 2.006s (~) 0.595s 15 1.00x
💻 Local Next.js (Turbopack) 1.424s (+0.9%) 2.010s (~) 0.586s 15 1.01x
💻 Local Express 1.426s (-1.5%) 2.006s (~) 0.580s 15 1.01x
🐘 Postgres Nitro 1.999s (-5.3% 🟢) 2.597s (+2.7%) 0.598s 12 1.42x
🐘 Postgres Express 2.099s (+4.5%) 2.615s (~) 0.516s 12 1.49x
🐘 Postgres Next.js (Turbopack) 2.577s (+15.3% 🔺) 2.834s (~) 0.257s 11 1.83x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 2.768s (-2.3%) 3.721s (+2.1%) 0.953s 9 1.00x
▲ Vercel Express 2.795s (-3.9%) 3.775s (+2.4%) 0.980s 8 1.01x
▲ Vercel Nitro 2.837s (~) 4.354s (+16.6% 🔺) 1.518s 7 1.02x

🔍 Observability: Next.js (Turbopack) | Express | Nitro

Promise.race with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Nitro 2.647s (+13.2% 🔺) 3.011s (-9.0% 🟢) 0.364s 10 1.00x
💻 Local Next.js (Turbopack) 2.655s (+1.0%) 3.029s (~) 0.374s 10 1.00x
💻 Local Express 2.674s (-7.4% 🟢) 3.009s (-0.9%) 0.335s 10 1.01x
🐘 Postgres Nitro 11.265s (-7.7% 🟢) 11.714s (-5.2% 🟢) 0.449s 3 4.26x
🐘 Postgres Express 11.896s (-1.4%) 12.043s (-2.7%) 0.146s 3 4.49x
🐘 Postgres Next.js (Turbopack) 14.178s (+5.6% 🔺) 15.025s (+9.0% 🔺) 0.847s 2 5.36x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 2.990s (~) 3.811s (+2.0%) 0.821s 9 1.00x
▲ Vercel Express 3.070s (+1.2%) 3.943s (+8.4% 🔺) 0.873s 8 1.03x
▲ Vercel Next.js (Turbopack) 3.089s (+3.9%) 3.693s (-3.2%) 0.604s 9 1.03x

🔍 Observability: Nitro | Express | Next.js (Turbopack)

Promise.race with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 7.508s (+9.7% 🔺) 8.602s (+4.5%) 1.094s 4 1.00x
💻 Local Nitro 7.816s (+19.7% 🔺) 8.812s (+17.0% 🔺) 0.997s 4 1.04x
💻 Local Express 7.868s (-3.0%) 8.813s (+4.2%) 0.945s 4 1.05x
🐘 Postgres Nitro 48.419s (-9.3% 🟢) 49.153s (-9.3% 🟢) 0.734s 1 6.45x
🐘 Postgres Express 54.095s (+3.5%) 54.270s (+1.9%) 0.175s 1 7.20x
🐘 Postgres Next.js (Turbopack) 58.208s (+3.6%) 59.241s (+5.3% 🔺) 1.033s 1 7.75x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 3.248s (+2.3%) 3.838s (+1.3%) 0.589s 8 1.00x
▲ Vercel Next.js (Turbopack) 3.359s (+1.0%) 4.036s (+2.8%) 0.676s 8 1.03x
▲ Vercel Express 3.604s (-8.2% 🟢) 4.464s (-0.6%) 0.860s 8 1.11x

🔍 Observability: Nitro | Next.js (Turbopack) | Express

Stream Benchmarks (includes TTFB metrics)
workflow with stream

💻 Local Development

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 0.143s (+1.5%) 1.003s (~) 0.015s (+2.7%) 1.026s (~) 0.882s 10 1.00x
💻 Local Express 0.180s (-4.9%) 0.992s (~) 0.014s (-5.4% 🟢) 1.020s (~) 0.840s 10 1.25x
💻 Local Nitro 0.181s (+56.6% 🔺) 0.992s (-0.8%) 0.014s (+19.8% 🔺) 1.020s (~) 0.840s 10 1.26x
🐘 Postgres Next.js (Turbopack) 0.641s (-46.2% 🟢) 0.955s (-48.5% 🟢) 0.000s (+Infinity% 🔺) 1.016s (-49.7% 🟢) 0.375s 10 4.47x
🐘 Postgres Express 2.328s (-2.1%) 2.717s (+1.9%) 0.000s (-100.0% 🟢) 3.017s (~) 0.688s 10 16.23x
🐘 Postgres Nitro 2.386s (+108.2% 🔺) 2.657s (+40.2% 🔺) 0.000s (+200.0% 🔺) 3.016s (+49.7% 🔺) 0.629s 10 16.63x

▲ Production (Vercel)

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 3.084s (+8.1% 🔺) 3.413s (+4.2%) 0.222s (-1.8%) 4.129s (+3.9%) 1.044s 10 1.00x
▲ Vercel Express 3.109s (+3.6%) 3.466s (+4.1%) 0.227s (+41.2% 🔺) 4.303s (+8.5% 🔺) 1.194s 10 1.01x
▲ Vercel Next.js (Turbopack) 3.187s (+6.4% 🔺) 3.353s (+1.4%) 0.238s (+36.3% 🔺) 4.130s (+3.8%) 0.943s 10 1.03x

🔍 Observability: Nitro | Express | Next.js (Turbopack)

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World 🥇 Fastest Framework Wins
💻 Local Next.js (Turbopack) 8/12
🐘 Postgres Nitro 6/12
▲ Vercel Nitro 6/12
Fastest World by Framework

Winner determined by most benchmark wins

Framework 🥇 Fastest World Wins
Express 💻 Local 10/12
Next.js (Turbopack) 💻 Local 10/12
Nitro 💻 Local 10/12
Column Definitions
  • Workflow Time: Runtime reported by workflow (completedAt - createdAt) - primary metric
  • TTFB: Time to First Byte - time from workflow start until first stream byte received (stream benchmarks only)
  • Slurp: Time from first byte to complete stream consumption (stream benchmarks only)
  • Wall Time: Total testbench time (trigger workflow + poll for result)
  • Overhead: Testbench overhead (Wall Time - Workflow Time)
  • Samples: Number of benchmark iterations run
  • vs Fastest: How much slower compared to the fastest configuration for this benchmark

Worlds:

  • 💻 Local: In-memory filesystem world (local development)
  • 🐘 Postgres: PostgreSQL database world (local development)
  • ▲ Vercel: Vercel production/preview deployment
  • 🌐 Starter: Community world (local development)
  • 🌐 Turso: Community world (local development)
  • 🌐 MongoDB: Community world (local development)
  • 🌐 Redis: Community world (local development)
  • 🌐 Jazz: Community world (local development)

📋 View full workflow run

@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented Feb 5, 2026 •
edited
Loading

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
example-nextjs-workflow-turbopack Ready Ready Preview, Comment, Open in v0 Feb 5, 2026 7:12am
example-nextjs-workflow-webpack Ready Ready Preview, Comment, Open in v0 Feb 5, 2026 7:12am
example-workflow Ready Ready Preview, Comment, Open in v0 Feb 5, 2026 7:12am
workbench-astro-workflow Ready Ready Preview, Comment, Open in v0 Feb 5, 2026 7:12am
workbench-express-workflow Ready Ready Preview, Comment, Open in v0 Feb 5, 2026 7:12am
workbench-fastify-workflow Ready Ready Preview, Comment, Open in v0 Feb 5, 2026 7:12am
workbench-hono-workflow Ready Ready Preview, Comment, Open in v0 Feb 5, 2026 7:12am
workbench-nitro-workflow Ready Ready Preview, Comment, Open in v0 Feb 5, 2026 7:12am
workbench-nuxt-workflow Ready Ready Preview, Comment, Open in v0 Feb 5, 2026 7:12am
workbench-sveltekit-workflow Ready Ready Preview, Comment, Open in v0 Feb 5, 2026 7:12am
workbench-vite-workflow Ready Ready Preview, Comment, Open in v0 Feb 5, 2026 7:12am
workflow-docs Ready Ready Preview, Comment, Open in v0 Feb 5, 2026 7:12am
workflow-nest Ready Ready Preview, Comment, Open in v0 Feb 5, 2026 7:12am
workflow-swc-playground Ready Ready Preview, Comment, Open in v0 Feb 5, 2026 7:12am

@TooTallNate Graphite App
Copy link
Copy Markdown
Member Author

TooTallNate commented Feb 5, 2026

This stack of pull requests is managed by Graphite. Learn more about stacking.

@TooTallNate TooTallNate marked this pull request as ready for review February 5, 2026 07:11
Copilot AI review requested due to automatic review settings February 5, 2026 07:11
Copilot AI reviewed Feb 5, 2026
View reviewed changes
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR enhances debugging capabilities for Windows E2E tests by capturing, displaying, and preserving Next.js server logs. Previously, server output was invisible in test runs, making it difficult to diagnose server-side failures on Windows.

Changes:

  • Modified log capture to redirect Next.js server output to a log file during E2E test execution
  • Added post-test step to print captured logs to the GitHub Actions console
  • Added artifact upload step to preserve logs for later inspection

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
.github/workflows/tests.yml Added log file capture, console printing, and artifact upload for Next.js server logs in Windows E2E tests
.changeset/fruity-ads-write.md Empty changeset file for CI/workflow-only changes (no package changes)

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@TooTallNate TooTallNate merged commit c28d6ca into main Feb 5, 2026
161 of 162 checks passed
@TooTallNate TooTallNate deleted the 02-04-upload_next.js_server_logs_as_artifact_for_windows_e2e branch February 5, 2026 19:10
pranaygp added a commit that referenced this pull request Feb 6, 2026
@pranaygp
Merge remote-tracking branch 'origin/main' into pranaygp/step-handler…
15e4d4a 
…-parallelization

* origin/main:
  Remove "beads" config (#952)
  Upload Next.js server logs as artifact for Windows E2E (#946)
  Pass class as `this` context to custom serializer/deserializer methods (#947)
  [docs] Fix image link in NestJS getting started guide (#941)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

Copilot code review Copilot Copilot left review comments

@ijjk ijjk ijjk approved these changes

@VaguelySerious VaguelySerious VaguelySerious approved these changes

@pranaygp pranaygp Awaiting requested review from pranaygp

@karthikscale3 karthikscale3 Awaiting requested review from karthikscale3

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@TooTallNate @ijjk @VaguelySerious