Uh oh!
There was an error while loading. Please reload this page.
fix(e2e): increase utf8StreamWorkflow test timeout to 120s - #1869
Conversation
Matches the convention used by readableStreamWorkflow and webhookWorkflow. The 60s budget is too tight when a single Vercel Queue delivery retry can take 30-60s, causing intermittent flakiness on the nitro workbench. Made-with: Cursor
|
📊 Benchmark Results
workflow with no steps💻 Local Development
workflow with 1 step💻 Local Development
workflow with 10 sequential steps💻 Local Development
workflow with 25 sequential steps💻 Local Development
workflow with 50 sequential steps💻 Local Development
Promise.all with 10 concurrent steps💻 Local Development
Promise.all with 25 concurrent steps💻 Local Development
Promise.all with 50 concurrent steps💻 Local Development
Promise.race with 10 concurrent steps💻 Local Development
Promise.race with 25 concurrent steps💻 Local Development
Promise.race with 50 concurrent steps💻 Local Development
workflow with 10 sequential data payload steps (10KB)💻 Local Development
workflow with 25 sequential data payload steps (10KB)💻 Local Development
workflow with 50 sequential data payload steps (10KB)💻 Local Development
workflow with 10 concurrent data payload steps (10KB)💻 Local Development
workflow with 25 concurrent data payload steps (10KB)💻 Local Development
workflow with 50 concurrent data payload steps (10KB)💻 Local Development
Stream Benchmarks(includes TTFB metrics)workflow with stream💻 Local Development
stream pipeline with 5 transform steps (1MB)💻 Local Development
10 parallel streams (1MB each)💻 Local Development
fan-out fan-in 10 streams (1MB each)💻 Local Development
SummaryFastest Framework by WorldWinner determined by most benchmark wins
Fastest World by FrameworkWinner determined by most benchmark wins
Column Definitions
Worlds:
|
🧪 E2E Test Results✅ All tests passed Summary
Details by Category✅ ▲ Vercel Production
✅ 💻 Local Development
✅ 📦 Local Production
✅ 🐘 Local Postgres
✅ 🪟 Windows
✅ 📋 Other
|
Uh oh!
There was an error while loading. Please reload this page.
Summary
utf8StreamWorkflowe2e test timeout from60_000to120_000ms to fix intermittent failures on the nitro workbenchRoot cause
The test was added in #1852 with a 60s timeout, but occasionally fails when the 4th sequential step (
'مرحبا بالعالم') isstep_createdbut neverstep_started— meaning a Vercel Queue delivery is dropped and must be retried. A retry can take 30–60s, which exhausts the 60s budget.This is infrastructure flakiness, not a code bug — the same test passes in most CI runs and the Arabic text is coincidental (it's just the 4th step). The convention for streaming workflow tests (
readableStreamWorkflow,webhookWorkflow) is120_000ms, which gives enough headroom for one retry cycle.Test plan
Made with Cursor