Skip to content

[next] Cover hybrid serializer + step modules across dev HMR - #4612

Closed
VaguelySerious wants to merge 1 commit into
mainfrom
peter/hmr-hybrid-serde-test
Closed

VaguelySerious wants to merge 1 commit into
mainfrom
peter/hmr-hybrid-serde-test

Conversation

@VaguelySerious

Copy link
Copy Markdown
Member

Ports the one piece of #3471 worth keeping onto current main: a dev e2e test for a module that defines both a custom-serialized class and a step that takes that class as an argument. Passing the class into the step makes the step bundle deserialize it, so the class has to stay registered there across dev rebuilds. Nothing on main exercised that: the existing body-only HMR fuzz test edits its serializer file, but its class never crosses a step boundary.

What it checks

One test, should keep a hybrid serializer + step module deserializable across HMR edits, in three phases:

  1. Round trip before any edit.
  2. After a body-only edit of an unrelated step file. This is the rebuild during which test(next): cover HMR rebuild convergence #3471 failed.
  3. After editing the serializer itself.

Result: passes on main

Locally on nextjs-turbopack (stable, node) all three phases pass. The dev server classified phase 2 as skip and phase 3 as hot rebuild with step registration refresh.

#3471's failure on all 8 Next dev lanes (Class "HmrFuzzBox" not found) was not an HMR bug. It came from the fixture declaring static classId = 'HmrFuzzBox' by hand:

  • The SWC plugin registers each class under its generated id (class//./workflows/<file>//<Name>). It assigns classId only when the class doesn't already define one (the hasOwnProperty guard in swc-plugin-workflow/spec.md).
  • A hand-written classId therefore goes into the payload, but no registry entry has that key, so the step fails to deserialize.

I reproduced this with the hand-written classId on a cold dev start, with the fixture on disk before the server started and zero HMR rebuilds. It failed identically there. Removing that one line made it pass. The fixture here has no hand-written classId, and a comment explains why.

Follow-ups (not in this PR)

  • main's existing fuzz fixture (hmr-fuzz-serde.ts in dev.test.ts) also declares static classId = 'HmrFuzzBox'. It is harmless there only because that class never crosses a boundary, but it is the pattern that misled test(next): cover HMR rebuild convergence #3471.
  • Product footgun: a user who writes their own static classId gets no build-time error, just a runtime Class "..." not found on the deserializing side. The docs never mention a custom classId, but nothing rejects one either. The fix is either to register under the existing classId as well, or to warn at build time.

Changeset is empty (test only).

🤖 Generated with Claude Code

Adds a dev e2e test for a module that defines both a custom-serialized
class and a step taking that class as an argument, so crossing the step
boundary deserializes the class inside the step bundle. It checks the
round trip before any edit, after a body-only edit of an unrelated step
file, and after an edit of the serializer itself.

The fixture deliberately has no hand-written `static classId`: the SWC
plugin registers the class under its generated id and only assigns
`classId` when the class has none, so a custom one never resolves on the
deserializing side.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@changeset-bot

changeset-bot Bot commented Oct 2, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 40b39ce

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

@vercel

vercel Bot commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

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

Project Deployment Actions Updated
example-nextjs-workflow-turbopack Ready Ready Preview, v0 Oct 2, 2026 10:59pm UTC
example-nextjs-workflow-webpack Ready Ready Preview, v0 Oct 2, 2026 10:59pm UTC
example-workflow Ready Ready Preview, v0 Oct 2, 2026 10:59pm UTC
workbench-astro-workflow Ready Ready Preview, v0 Oct 2, 2026 10:59pm UTC
workbench-express-workflow Ready Ready Preview, v0 Oct 2, 2026 10:59pm UTC
workbench-fastify-workflow Ready Ready Preview, v0 Oct 2, 2026 10:59pm UTC
workbench-hono-workflow Ready Ready Preview, v0 Oct 2, 2026 10:59pm UTC
workbench-nestjs-workflow Ready Ready Preview, v0 Oct 2, 2026 10:59pm UTC
workbench-nitro-workflow Ready Ready Preview, v0 Oct 2, 2026 10:59pm UTC
workbench-nuxt-workflow Ready Ready Preview, v0 Oct 2, 2026 10:59pm UTC
workbench-python-workflow Ready Ready Preview, v0 Oct 2, 2026 10:59pm UTC
workbench-sveltekit-workflow Ready Ready Preview, v0 Oct 2, 2026 10:59pm UTC
workbench-tanstack-start-workflow Ready Ready Preview, v0 Oct 2, 2026 10:59pm UTC
workbench-vite-workflow Ready Ready Preview, v0 Oct 2, 2026 10:59pm UTC
workflow-docs Ready Ready Preview, v0 Oct 2, 2026 10:59pm UTC
workflow-swc-playground Ready Ready Preview, v0 Oct 2, 2026 10:59pm UTC
workflow-tarballs Ready Ready Preview, v0 Oct 2, 2026 10:59pm UTC
workflow-web Ready Ready Preview, v0 Oct 2, 2026 10:59pm UTC

@github-actions

github-actions Bot commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

✅ All tests passed

⚠️ Flaky E2E Tests (passed on retry)

These tests failed at least once and passed on a retry. A recurring entry here is a real race worth investigating.

  • parallelStepsThenWebhookWorkflow - no hook_conflict from same-tick replay race (nextjs-webpack · local-dev / local / node / stable)
  • readableStreamWorkflow (nextjs-webpack · local-dev / local / node / stable)
  • sleepingWorkflow (nextjs-webpack · local-dev / local / node / stable)
  • webhookWorkflow (nextjs-webpack · local-dev / local / node / stable)

🛠 Infra Events (absorbed by the harness)

Platform anomalies the e2e harness detected and worked around (e.g. a run the queue never picked up, replaced by a fresh run). Clustered timestamps indicate a backend blip; a steady drip indicates a platform issue worth escalating.

  • run-pickup-stall · runs app-generated source against a registered step (tanstack-start) · at 23:01:49Z · abandoned wrun_01M3ZDKZFGXDYCQ2080SGEET3G
  • cold-start-warmup · suite warmup (tanstack-start) · at 23:01:49Z · abandoned wrun_01M3ZDKZG6YYSGEDBSRDSVP7NC
  • run-pickup-stall · ChainableService.processWithThis - static step methods using this to reference the class (nextjs-turbopack) · at 23:04:33Z · abandoned wrun_01M3ZDS08RJ4MA2NH86YEPN3SB
  • run-pickup-stall · hookCleanupTestWorkflow - hook token reuse after workflow completion (nextjs-webpack) · at 23:09:37Z · abandoned wrun_01M3ZE28TR8KX337J65DPHD22R

E2E Test Summary

Summary
Passed Failed Skipped Total
✅ ▲ Vercel Production 3904 0 875 4779
✅ 💻 Local Development 4582 0 551 5133
✅ 📦 Local Production 4582 0 551 5133
✅ 🐘 Local Postgres 4582 0 551 5133
✅ 🪟 Windows 342 0 12 354
✅ 🌐 Cross-language Conformance 68 0 84 152
✅ dynamic-runs 0 0 0 0
✅ vercel-http-transport 879 0 183 1062
✅ vercel-multi-region 27 0 0 27
✅ vercel-ws-transport 595 0 113 708
Total 19561 0 2920 22481
Details by Category

✅ ▲ Vercel Production

App Passed Failed Skipped
✅ astro-node 142 0 35
✅ astro-quickjs 142 0 35
✅ example-node 142 0 35
✅ example-quickjs 142 0 35
✅ express-node 142 0 35
✅ express-quickjs 142 0 35
✅ fastify-node 142 0 35
✅ fastify-quickjs 142 0 35
✅ hono-node 142 0 35
✅ hono-quickjs 142 0 35
✅ nest-node 142 0 35
✅ nest-quickjs 142 0 35
✅ nextjs-turbopack-node 169 0 8
✅ nextjs-turbopack-quickjs 169 0 8
✅ nextjs-webpack-node 169 0 8
✅ nextjs-webpack-quickjs 169 0 8
✅ nitro-node 142 0 35
✅ nitro-quickjs 142 0 35
✅ nuxt-node 142 0 35
✅ nuxt-quickjs 142 0 35
✅ python-node 66 0 111
✅ sveltekit-node 161 0 16
✅ sveltekit-quickjs 161 0 16
✅ tanstack-start-node 142 0 35
✅ tanstack-start-quickjs 142 0 35
✅ vite-node 142 0 35
✅ vite-quickjs 142 0 35

✅ 💻 Local Development

App Passed Failed Skipped
✅ astro-stable-node 148 0 29
✅ astro-stable-quickjs 148 0 29
✅ express-stable-node 148 0 29
✅ express-stable-quickjs 148 0 29
✅ fastify-stable-node 148 0 29
✅ fastify-stable-quickjs 148 0 29
✅ hono-stable-node 148 0 29
✅ hono-stable-quickjs 148 0 29
✅ nest-stable-node 148 0 29
✅ nest-stable-quickjs 148 0 29
✅ nextjs-turbopack-canary-node 176 0 1
✅ nextjs-turbopack-canary-quickjs 176 0 1
✅ nextjs-turbopack-quickjs-snapshot 176 0 1
✅ nextjs-turbopack-stable-node 176 0 1
✅ nextjs-turbopack-stable-quickjs 176 0 1
✅ nextjs-webpack-canary-node 176 0 1
✅ nextjs-webpack-canary-quickjs 176 0 1
✅ nextjs-webpack-stable-node 176 0 1
✅ nextjs-webpack-stable-quickjs 176 0 1
✅ nitro-stable-node 148 0 29
✅ nitro-stable-quickjs 148 0 29
✅ nuxt-stable-node 148 0 29
✅ nuxt-stable-quickjs 148 0 29
✅ sveltekit-stable-node 167 0 10
✅ sveltekit-stable-quickjs 167 0 10
✅ tanstack-start-node 148 0 29
✅ tanstack-start-quickjs 148 0 29
✅ vite-stable-node 148 0 29
✅ vite-stable-quickjs 148 0 29

✅ 📦 Local Production

App Passed Failed Skipped
✅ astro-stable-node 148 0 29
✅ astro-stable-quickjs 148 0 29
✅ express-stable-node 148 0 29
✅ express-stable-quickjs 148 0 29
✅ fastify-stable-node 148 0 29
✅ fastify-stable-quickjs 148 0 29
✅ hono-stable-node 148 0 29
✅ hono-stable-quickjs 148 0 29
✅ nest-stable-node 148 0 29
✅ nest-stable-quickjs 148 0 29
✅ nextjs-turbopack-canary-node 176 0 1
✅ nextjs-turbopack-canary-quickjs 176 0 1
✅ nextjs-turbopack-quickjs-snapshot 176 0 1
✅ nextjs-turbopack-stable-node 176 0 1
✅ nextjs-turbopack-stable-quickjs 176 0 1
✅ nextjs-webpack-canary-node 176 0 1
✅ nextjs-webpack-canary-quickjs 176 0 1
✅ nextjs-webpack-stable-node 176 0 1
✅ nextjs-webpack-stable-quickjs 176 0 1
✅ nitro-stable-node 148 0 29
✅ nitro-stable-quickjs 148 0 29
✅ nuxt-stable-node 148 0 29
✅ nuxt-stable-quickjs 148 0 29
✅ sveltekit-stable-node 167 0 10
✅ sveltekit-stable-quickjs 167 0 10
✅ tanstack-start-node 148 0 29
✅ tanstack-start-quickjs 148 0 29
✅ vite-stable-node 148 0 29
✅ vite-stable-quickjs 148 0 29

✅ 🐘 Local Postgres

App Passed Failed Skipped
✅ astro-stable-node 148 0 29
✅ astro-stable-quickjs 148 0 29
✅ express-stable-node 148 0 29
✅ express-stable-quickjs 148 0 29
✅ fastify-stable-node 148 0 29
✅ fastify-stable-quickjs 148 0 29
✅ hono-stable-node 148 0 29
✅ hono-stable-quickjs 148 0 29
✅ nest-stable-node 148 0 29
✅ nest-stable-quickjs 148 0 29
✅ nextjs-turbopack-canary-node 176 0 1
✅ nextjs-turbopack-canary-quickjs 176 0 1
✅ nextjs-turbopack-quickjs-snapshot 176 0 1
✅ nextjs-turbopack-stable-node 176 0 1
✅ nextjs-turbopack-stable-quickjs 176 0 1
✅ nextjs-webpack-canary-node 176 0 1
✅ nextjs-webpack-canary-quickjs 176 0 1
✅ nextjs-webpack-stable-node 176 0 1
✅ nextjs-webpack-stable-quickjs 176 0 1
✅ nitro-stable-node 148 0 29
✅ nitro-stable-quickjs 148 0 29
✅ nuxt-stable-node 148 0 29
✅ nuxt-stable-quickjs 148 0 29
✅ sveltekit-stable-node 167 0 10
✅ sveltekit-stable-quickjs 167 0 10
✅ tanstack-start-node 148 0 29
✅ tanstack-start-quickjs 148 0 29
✅ vite-stable-node 148 0 29
✅ vite-stable-quickjs 148 0 29

✅ 🪟 Windows

App Passed Failed Skipped
✅ nextjs-turbopack-node 171 0 6
✅ nextjs-turbopack-quickjs 171 0 6

✅ 🌐 Cross-language Conformance

App Passed Failed Skipped
✅ python 68 0 84

✅ dynamic-runs

App Passed Failed Skipped
✅ astro-vercel 0 0 0
✅ example-vercel 0 0 0
✅ express-vercel 0 0 0
✅ fastify-vercel 0 0 0
✅ hono-vercel 0 0 0
✅ nest-vercel 0 0 0
✅ nextjs-turbopack-vercel 0 0 0
✅ nextjs-webpack-vercel 0 0 0
✅ nitro-vercel 0 0 0
✅ nuxt-vercel 0 0 0
✅ sveltekit-vercel 0 0 0
✅ tanstack-start-vercel 0 0 0
✅ vite-vercel 0 0 0

✅ vercel-http-transport

App Passed Failed Skipped
✅ example 142 0 35
✅ express 142 0 35
✅ hono 142 0 35
✅ nextjs-turbopack 169 0 8
✅ nitro 142 0 35
✅ vite 142 0 35

✅ vercel-multi-region

App Passed Failed Skipped
✅ nextjs-turbopack 27 0 0

✅ vercel-ws-transport

App Passed Failed Skipped
✅ example 142 0 35
✅ express 142 0 35
✅ nextjs-turbopack 169 0 8
✅ vite 142 0 35

📋 View full workflow run

@github-actions

github-actions Bot commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

📊 Workflow Benchmarks

commit 40b39ce · Fri, 02 Oct 2026 23:22:31 GMT · run logs

Backend: vercel · app: nextjs-turbopack

Metric Scenario Best (ms) P75 (ms) P90 (ms) P99 (ms) Samples
TTFS step 2244 (+820%) 🔻 2700 🔴 (+52%) 🔻 2771 🔴 (+43%) 🔻 2781 🔴 (+10%) 30
TTFS stream 2227 (+681%) 🔻 2676 🔴 (+48%) 🔻 2721 🔴 (+48%) 🔻 2928 🔴 (+38%) 🔻 30
TTFS hook + stream 2271 (+152%) 🔻 2625 🔴 (+23%) 🔻 2852 🔴 (+29%) 🔻 5588 🔴 (+32%) 🔻 30
Fan-out TTFS Promise.all(100 steps) 510 (-4.7%) 685 (-19%) 💚 707 (-67%) 💚 2765 (+5.4%) 10
Fan-out TTLS Promise.all(100 steps) 1528 (+2.8%) 3049 (+20%) 🔻 3051 (-23%) 💚 8836 (+58%) 🔻 10
STSO 1020 steps (inline) 104 (-13%) 133 (-16%) 💚 152 (-19%) 💚 216 (-40%) 💚 1019
WO 1020 steps 133948 (-15%) 💚 133948 (-15%) 💚 133948 (-15%) 💚 133948 (-15%) 💚 1
CRTT first chunk (pooled) 72 (+1.4%) 96 (-21%) 💚 330 (+109%) 🔻 3216 (+660%) 🔻 28

Streams

Scenario CRTT 1st p75 p90 p99 CDV max iters
paced control (100/s, 60B) 92.5 (-5%) 185 (-11%) 2469 (+345%) 3073 (+68%) 144 (-43%) 10
size sweep (100/s, 160B-12KB) 84 (-15%) 164 (-25%) 214 (-34%) 3191 (+400%) 160 (-23%) 10
replay gateway-gpt-5.4-nano-2000t (1x) 82 (-13%) 153 (-13%) 191 (-17%) 322 (-51%) 174 (-39%) 3
replay eve-gpt-5.6-sol-2000t (1x) 104 (-50%) 145 (-43%) 176 (-78%) 271 (-85%) 196 (-78%) 2
replay eve-gpt-5.6-sol-2000t (2x) 81 (-33%) 174 (-28%) 213 (-41%) 311 (-64%) 205 (-62%) 3
📈 STSO distribution vs main (inline / queue-hop histograms)

1020 steps (inline)

Cumulative STSO time: main 157838ms → this run 133578ms (Δ -24260ms, -15%)

100-150 ms  ██████████████████░░░░░┃  main 687  this 903  +216
150-200 ms  ██┃████                   main 252  this 101  -151
200-250 ms  ┃                         main  42  this  11   -31
250-300 ms  ┃                         main  16  this   3   -13
300-350 ms  ┃                         main  11  this   1   -10
350-400 ms  ┃                         main   5  this   0    -5
400-450 ms  ┃                         main   1  this   0    -1
450-500 ms  ┃                         main   1  this   0    -1
500-550 ms  ┃                         main   1  this   0    -1
550-600 ms  ┃                         main   1  this   0    -1
600-650 ms  ┃                         main   1  this   0    -1
850-900 ms  ┃                         main   1  this   0    -1
📈 CRTT drill-down vs main (RTT distributions & profiles)
variant  RTT 1ms→5s+             avg         p50           p90           p99     n
control  ······▃█▂▁▁▁·  308.8 (+61%)   131 (-9%)  2469 (+345%)   3073 (+68%)  3000
sweep    ······▃█▂▁▁▁·  302.3 (+84%)  126 (-12%)    214 (-34%)  3191 (+400%)  3000
gw 1x    ·····▁▄█▁····  124.4 (-19%)  117 (-16%)    191 (-17%)    322 (-51%)  5295
eve 1x   ·····▁▅█▁····  120.7 (-49%)  113 (-23%)    176 (-78%)    271 (-85%)  5186
eve 2x   ·····▁▃█▂····  141.4 (-28%)  131 (-19%)    213 (-41%)    311 (-64%)  7779

RTT over stream progress (avg per tenth of stream, bars scaled min→max):

control  █▇▆▄▄▃▁▁██  180–405ms
sweep    █▇▆▆▅▄▃▂▂▁  178–433ms
gw 1x    ▇▃▁▅▂█▅▂▂▂  117–137ms
eve 1x   ▃▁▇▃▂▆█▇▅▁  113–129ms
eve 2x   ▂▂▂▂▁▃▆█▆▄  122–175ms

RTT by chunk size (avg per log size bin, ~160B → ~12KB serialized, bars scaled min→max):

sweep  ▆▂▁▂█▄▃  301–305ms

Delivery jitter over stream progress (avg positive CDV per tenth of stream, bars scaled min→max):

control  ▁▂▂▁▁▂▁▂█▁  37–127ms
sweep    ▃▁▅▄▆▅▃▆█▆  47–67ms
gw 1x    █▅▁▄▅▅▅▅▄▃  34–44ms
eve 1x   ▃▃▄▅▁▂██▂█  23–26ms
eve 2x   ▇▆▁▄▆▄▇▂▄█  20–30ms
ℹ️ Metric definitions & methodology

Streams: first-chunk RTT (the stream-open path, before any buffering/backpressure), CRTT percentiles, and worst delivery stall (CDV max). Cells are medians across iterations; per-run values in the artifacts. No 🔴/🟢 marks until targets attach.

The collapsed STSO distribution section above buckets every step gap, split inline (same warm process — pure framework overhead) vs queue-hop (fresh process — dispatch, reinit, replay). █ = main, ┃ = this run, ░ = fill.

The collapsed CRTT drill-down: per-variant RTT histograms (fixed log bins, · = empty) and mean RTT/positive-CDV profile lines over stream progress and chunk size. Histograms, avgs, and profiles merge exactly across runs; p50–p99 are percentile-of-percentiles. Per-index rows live in the artifacts.

Best/P75/P90/P99 deltas compare against the most recent benchmark run on main at the time of this run. 🔻 flags a delta worse than +15%, 💚 one better than −15%.

Metrics — TTFS: time to first step body (in-deployment start() → first step body) · Fan-out TTFS: fan-out time to first step (in-deployment start() → first of the parallel step bodies to complete) · Fan-out TTLS: fan-out time to last step (in-deployment start() → last of the parallel step bodies to complete, i.e. when the Promise.all resolves) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · CRTT: chunk round-trip time (per-chunk write → read latency, one clock domain: deployment → stream backend → same deployment) · CDV: chunk delay variation / delivery jitter (inter-arrival gap minus inter-write gap per seq-adjacent pair; skew-free; the row is each run's MAX positive value, so one stall moves it)

Scenarios — step: one trivial no-op step, no stream; no hooks, so the run stays in turbo mode (in-process fast path) · stream: one streaming step; no hooks, so the run stays in turbo mode (in-process fast path) · hook + stream: registers a hook before one step, which exits turbo mode (dispatch path) · 1020 steps: 1020 trivial sequential steps; STSO is measured between consecutive steps in the given step ranges, and WO is the whole-run overhead outside step bodies · Promise.all(100 steps): 100 trivial no-op steps started together in a single Promise.all; Fan-out TTFS is the first of them to complete and Fan-out TTLS the last, both from the in-deployment clientStart, so their gap is the spread the runtime adds across the fan-out · paced control (100/s, 60B): the control: 300 tiny (~60B) deltas metronome-paced at 100/s — zero workload structure, so it reads the transport floor and flush cadence, and disambiguates transport-wide vs workload-specific when a replay row moves · size sweep (100/s, 160B-12KB): same pacing as the control with deltas padded in rotation across seven log-spaced sizes (~160B–12KB) — rotation decouples size from stream position, so it isolates whether chunk size causes latency · replay gateway-gpt-5.4-nano-2000t (1x): raw provider SSE cadence captured at the AI gateway boundary (gpt-5.4-nano, the most popular gateway model; per-token deltas p50 208B = the modal production chunk size), replayed exactly as measured — the typical customer's workload; its CDV is the typical customer's real delivery jitter · replay eve-gpt-5.6-sol-2000t (1x): a captured eve turn (gpt-5.6-sol, the most-used demanding eve model; ~2000 output tokens = production p50 turn length) replayed exactly as measured — eve's envelope protocol re-ships the cumulative message so sizes ramp 142B→13KB; the demanding outlier tenant's reality · replay eve-gpt-5.6-sol-2000t (2x): the same eve capture at 2x — the headroom/stress row; real fast-tier models emit the same chunk sizes at proportionally higher rate, so time compression is a faithful speed model · first chunk (pooled): every run's seq-0 RTT pooled across all stream scenarios — the first chunk precedes any workload differentiation, so pooling samples one shared stream-open path with exact percentiles

Replay cadences (semantic sha256) — eve-gpt-5.6-sol-2000t eaf22f5946e7c61f3c65c7006d550df180cfabd4e706254a09f22aec0cfb420d · gateway-gpt-5.4-nano-2000t 6f24ac518b6b83ff1d0e85a5fe78230db192716d66a7fc6b2fe022752001d041

🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600

All timestamps are deployment-side; runs are triggered in-deployment, so the CI runner and api.vercel.com sit outside every measured window. TTFS = start() → first step body (includes dispatch + any cold start); Fan-out TTFS/TTLS = first/last step completion of one Promise.all from the same anchor (the gap is the runtime’s fan-out spread); STSO/WO between step bodies; CRTT inside the workflow (excludes the api.vercel.com read path).

Cold starts stay in the numbers (real bursty-workload latency, inflates P75+); Best is the warm floor.

@github-actions

github-actions Bot commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

Sim World

Simulated world deterministic testing for races. Traces

🟠 world-sim scenario book — 1 fail of 42 total

fence=per-spec

scenario outcome events virt replay violations
✅ smoke-no-steps completed 3 0ms ok 0
✅ smoke-one-step completed 6 0ms ok 0
✅ hook-at-step-started completed 12 0ms ok 0
✅ hook-at-step-completed completed 12 0ms ok 0
✅ hook-at-hook-created completed 12 0ms ok 0
✅ deadline-hook-wins completed 7 1.0h ok 0
✅ deadline-expires completed 7 1.0h ok 0
✅ step-vs-timer-early-settlement completed 8 1.0h ok 0
✅ long-sleep completed 11 30.0d ok 0
✅ hook-never-arrives stalled 3 0ms skipped 0
✅ step-retries-twice completed 10 2.0s ok 0
✅ parallel-steps completed 9 0ms ok 0
✅ hook-on-execution-state completed 12 0ms ok 0
✅ peek-hook-before-branch completed 12 0ms ok 0
✅ peek-hook-after-branch completed 12 0ms ok 0
✅ peek-hook-at-registration completed 12 0ms ok 0
✅ race-hook-before-probe completed 12 0ms ok 0
✅ race-hook-after-probe completed 12 0ms ok 0
✅ race-duplicate-delivery completed 13 0ms ok 0
✅ attr-hook-before-step completed 11 0ms ok 0
✅ attr-hook-after-step completed 11 0ms ok 0
✅ attr-from-step-body completed 13 0ms ok 0
✅ fork-hook-after-timeout completed 14 1.0m ok 0
✅ fork-hook-before-timeout completed 14 1.0m ok 0
✅ count-hook-after-timeout completed 17 1.0m ok 0
✅ count-hook-before-timeout completed 20 1.0m ok 0
✅ stale-read-step-count-fork completed 20 1.0m ok 0
✅ stale-read-equal-step-counts completed 14 1.0m ok 0
✅ step-vs-step-fork completed 12 0ms ok 0
✅ step-vs-step-fork-fenced completed 12 0ms ok 0
✅ fence-catches-benign-direction completed 12 5ms ok 0
✅ in-flight-before-decision completed 17 1.0m ok 0
❌ in-flight-before-decision-counted completed 17 1.0m ok 0
✅ in-flight-after-decision completed 19 2.0m ok 0
✅ stale-read-step-count-fork-fenced completed 20 1.0m ok 0
✅ fork-hook-wins completed 13 1.0m ok 0
✅ fork-timeout-wins completed 13 1.0m ok 0
✅ unclaimed-payload-under-fork completed 17 1.0m ok 0
✅ claimed-payload-under-fork completed 17 1.0m ok 0
✅ writers-independent-step-bodies completed 12 0ms ok 0
✅ writers-scripted-tempo completed 12 0ms ok 0
✅ cancel-mid-step cancelled 7 0ms skipped 0

Full trace: world-sim.txt

@github-actions

github-actions Bot commented Oct 2, 2026

Copy link
Copy Markdown
Contributor
Framework Flow route Step reg. Framework output
hono 267.2 KiB (±0) 97.3 KiB (±0) 2.01 MiB (±0)
nextjs-turbopack 274.6 KiB (±0) 426 B (±0) 986.2 KiB (±0)
About these numbers

Sizes are gzip; parentheses show the change against main.
Flow route and Step reg. gate this job, on raw bytes rather than the gzip shown, at max(2%, 50.0 KiB). Framework output is informational.

40b39ce · run

This branch was successfully deployed

1 active deployment
Preview – workflow-docs — 40b39ce4 Deployed Oct 2, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant