Skip to content

[ci] Bump Next.js canary e2e pin to 16.3.1-canary.17 - #3559

Open
pranaygp wants to merge 1 commit into
mainfrom
pgp/bump-next-canary-pin
Open

[ci] Bump Next.js canary e2e pin to 16.3.1-canary.17#3559
pranaygp wants to merge 1 commit into
mainfrom
pgp/bump-next-canary-pin

Conversation

@pranaygp

Copy link
Copy Markdown
Contributor

Summary & Motivation

The canary e2e lanes (E2E Local Dev / Local Prod / Local Postgres for nextjs-turbopack and nextjs-webpack, × node/quickjs) were pinned to 16.3.0-canary.2. This bumps the pin to the current canary, 16.3.1-canary.17, in all six spots in tests.yml.

Bumping the pin alone is not enough: fresh Next canaries are younger than the repo's 48h minimumReleaseAge gate, so the "Setup canary" pnpm install --no-frozen-lockfile fails with ERR_PNPM_NO_MATURE_MATCHING_VERSION (reproduced locally with this exact version). This adds next and its lockstep-published @next/* companion packages (@next/env, @next/swc-*) to minimumReleaseAgeExclude — both are Vercel-published, matching the trust model of the existing exclusions (@vercel/*, turbo, esbuild).

Validation

The full e2e suite was run locally against next@16.3.1-canary.17 on all three worlds (staged tarball workbenches, same as CI's prepare-workbench-path):

World App / mode Result
world-local nextjs-webpack, dev server, node vm dev.test.ts 5 passed / 4 skipped (incl. the HMR fuzz test) · test:e2e 137 passed / 19 skipped
world-postgres nextjs-turbopack, prod build, node vm local-build.test.ts 13 passed · test:e2e 137 passed / 19 skipped¹
world-vercel nextjs-turbopack, preview deployment (dpl_3siALD2WyrsrdPFjmRY3ymwEHZiJ), node vm test:e2e 134 passed / 22 skipped

¹ First pass failed the 3 pages router tests because the local harness ran local-build.test.ts without CI=true, which deletes the workflow-sourcemap-warning-fixture package the built output still references (the test preserves it only when CI=true, exactly as its comment warns). With the fixture preserved, all 3 pass. Not a canary issue.

Note: the vercel world has no canary lane in CI (deployments build from the committed stable pin), so the preview-deployment run above is the only canary coverage it got.

Context on current main CI

Recent main runs are red, but not because of the canary pin: the dominant failure is the nextjs-webpack local-dev HMR fuzz race (SDK-side, fix in flight in #3529), which hits the stable and canary lanes alike; the rest are the known rotating vercel-prod flakes. The latest completed main run (with #3530's e2e retry) passed every canary lane and failed only the stable webpack dev lane.

🤖 Generated with Claude Code

The canary e2e lanes (Local Dev / Local Prod / Local Postgres for
nextjs-turbopack and nextjs-webpack) were pinned to 16.3.0-canary.2.
Bump the pin to the current canary, 16.3.1-canary.17.

Fresh canaries are younger than the repo's 48h minimumReleaseAge gate,
which rejects the pinned version at the "Setup canary" install step, so
exclude next and its lockstep-published @next/* companion packages from
the gate — both are Vercel-published, matching the existing exclusions
(@vercel/*, turbo, esbuild).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Copilot AI lite review requested due to automatic review settings August 14, 2026 18:30
@pranaygp
pranaygp requested a review from a team as a code owner August 14, 2026 18:30
@changeset-bot

changeset-bot Bot commented Aug 14, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: de1d17f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

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

Click here to learn what changesets are, and how to add one.

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

@vercel

vercel Bot commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

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

Project Deployment Actions Updated (UTC)
example-nextjs-workflow-turbopack Ready Ready Preview Aug 14, 2026 6:36pm
example-nextjs-workflow-webpack Ready Ready Preview Aug 14, 2026 6:36pm
example-workflow Ready Ready Preview Aug 14, 2026 6:36pm
workbench-astro-workflow Ready Ready Preview Aug 14, 2026 6:36pm
workbench-express-workflow Ready Ready Preview Aug 14, 2026 6:36pm
workbench-fastify-workflow Ready Ready Preview Aug 14, 2026 6:36pm
workbench-hono-workflow Ready Ready Preview Aug 14, 2026 6:36pm
workbench-nestjs-workflow Ready Ready Preview Aug 14, 2026 6:36pm
workbench-nitro-workflow Ready Ready Preview Aug 14, 2026 6:36pm
workbench-nuxt-workflow Ready Ready Preview Aug 14, 2026 6:36pm
workbench-python-workflow Error Error Aug 14, 2026 6:36pm
workbench-sveltekit-workflow Ready Ready Preview Aug 14, 2026 6:36pm
workbench-tanstack-start-workflow Ready Ready Preview Aug 14, 2026 6:36pm
workbench-vite-workflow Ready Ready Preview Aug 14, 2026 6:36pm
workflow-docs Ready Ready Preview, v0 Aug 14, 2026 6:36pm
workflow-swc-playground Ready Ready Preview Aug 14, 2026 6:36pm
workflow-tarballs Ready Ready Preview Aug 14, 2026 6:36pm
workflow-web Ready Ready Preview Aug 14, 2026 6:36pm

@github-actions

github-actions Bot commented Aug 14, 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.

  • webhookWorkflow (tanstack-start)

E2E Test Summary

Summary
Passed Failed Skipped Total
✅ ▲ Vercel Production 3466 0 590 4056
✅ 💻 Local Development 3810 0 558 4368
✅ 📦 Local Production 3810 0 558 4368
✅ 🐘 Local Postgres 3810 0 558 4368
✅ 🪟 Windows 312 0 0 312
✅ vercel-multi-region 27 0 0 27
Total 15235 0 2264 17499
Details by Category

✅ ▲ Vercel Production

App Passed Failed Skipped
✅ astro-node 128 0 28
✅ astro-quickjs 128 0 28
✅ example-node 128 0 28
✅ example-quickjs 128 0 28
✅ express-node 128 0 28
✅ express-quickjs 128 0 28
✅ fastify-node 128 0 28
✅ fastify-quickjs 128 0 28
✅ hono-node 128 0 28
✅ hono-quickjs 128 0 28
✅ nest-node 128 0 28
✅ nest-quickjs 128 0 28
✅ nextjs-turbopack-node 153 0 3
✅ nextjs-turbopack-quickjs 153 0 3
✅ nextjs-webpack-node 153 0 3
✅ nextjs-webpack-quickjs 153 0 3
✅ nitro-node 128 0 28
✅ nitro-quickjs 128 0 28
✅ nuxt-node 128 0 28
✅ nuxt-quickjs 128 0 28
✅ sveltekit-node 147 0 9
✅ sveltekit-quickjs 147 0 9
✅ tanstack-start-node 128 0 28
✅ tanstack-start-quickjs 128 0 28
✅ vite-node 128 0 28
✅ vite-quickjs 128 0 28

✅ 💻 Local Development

App Passed Failed Skipped
✅ astro-stable-node 130 0 26
✅ astro-stable-quickjs 130 0 26
✅ express-stable-node 130 0 26
✅ express-stable-quickjs 130 0 26
✅ fastify-stable-node 130 0 26
✅ fastify-stable-quickjs 130 0 26
✅ hono-stable-node 130 0 26
✅ hono-stable-quickjs 130 0 26
✅ nest-stable-node 130 0 26
✅ nest-stable-quickjs 130 0 26
✅ nextjs-turbopack-canary-node 137 0 19
✅ nextjs-turbopack-canary-quickjs 137 0 19
✅ nextjs-turbopack-stable-node 156 0 0
✅ nextjs-turbopack-stable-quickjs 156 0 0
✅ nextjs-webpack-canary-node 137 0 19
✅ nextjs-webpack-canary-quickjs 137 0 19
✅ nextjs-webpack-stable-node 156 0 0
✅ nextjs-webpack-stable-quickjs 156 0 0
✅ nitro-stable-node 130 0 26
✅ nitro-stable-quickjs 130 0 26
✅ nuxt-stable-node 130 0 26
✅ nuxt-stable-quickjs 130 0 26
✅ sveltekit-stable-node 149 0 7
✅ sveltekit-stable-quickjs 149 0 7
✅ tanstack-start-node 130 0 26
✅ tanstack-start-quickjs 130 0 26
✅ vite-stable-node 130 0 26
✅ vite-stable-quickjs 130 0 26

✅ 📦 Local Production

App Passed Failed Skipped
✅ astro-stable-node 130 0 26
✅ astro-stable-quickjs 130 0 26
✅ express-stable-node 130 0 26
✅ express-stable-quickjs 130 0 26
✅ fastify-stable-node 130 0 26
✅ fastify-stable-quickjs 130 0 26
✅ hono-stable-node 130 0 26
✅ hono-stable-quickjs 130 0 26
✅ nest-stable-node 130 0 26
✅ nest-stable-quickjs 130 0 26
✅ nextjs-turbopack-canary-node 137 0 19
✅ nextjs-turbopack-canary-quickjs 137 0 19
✅ nextjs-turbopack-stable-node 156 0 0
✅ nextjs-turbopack-stable-quickjs 156 0 0
✅ nextjs-webpack-canary-node 137 0 19
✅ nextjs-webpack-canary-quickjs 137 0 19
✅ nextjs-webpack-stable-node 156 0 0
✅ nextjs-webpack-stable-quickjs 156 0 0
✅ nitro-stable-node 130 0 26
✅ nitro-stable-quickjs 130 0 26
✅ nuxt-stable-node 130 0 26
✅ nuxt-stable-quickjs 130 0 26
✅ sveltekit-stable-node 149 0 7
✅ sveltekit-stable-quickjs 149 0 7
✅ tanstack-start-node 130 0 26
✅ tanstack-start-quickjs 130 0 26
✅ vite-stable-node 130 0 26
✅ vite-stable-quickjs 130 0 26

✅ 🐘 Local Postgres

App Passed Failed Skipped
✅ astro-stable-node 130 0 26
✅ astro-stable-quickjs 130 0 26
✅ express-stable-node 130 0 26
✅ express-stable-quickjs 130 0 26
✅ fastify-stable-node 130 0 26
✅ fastify-stable-quickjs 130 0 26
✅ hono-stable-node 130 0 26
✅ hono-stable-quickjs 130 0 26
✅ nest-stable-node 130 0 26
✅ nest-stable-quickjs 130 0 26
✅ nextjs-turbopack-canary-node 137 0 19
✅ nextjs-turbopack-canary-quickjs 137 0 19
✅ nextjs-turbopack-stable-node 156 0 0
✅ nextjs-turbopack-stable-quickjs 156 0 0
✅ nextjs-webpack-canary-node 137 0 19
✅ nextjs-webpack-canary-quickjs 137 0 19
✅ nextjs-webpack-stable-node 156 0 0
✅ nextjs-webpack-stable-quickjs 156 0 0
✅ nitro-stable-node 130 0 26
✅ nitro-stable-quickjs 130 0 26
✅ nuxt-stable-node 130 0 26
✅ nuxt-stable-quickjs 130 0 26
✅ sveltekit-stable-node 149 0 7
✅ sveltekit-stable-quickjs 149 0 7
✅ tanstack-start-node 130 0 26
✅ tanstack-start-quickjs 130 0 26
✅ vite-stable-node 130 0 26
✅ vite-stable-quickjs 130 0 26

✅ 🪟 Windows

App Passed Failed Skipped
✅ nextjs-turbopack-node 156 0 0
✅ nextjs-turbopack-quickjs 156 0 0

✅ vercel-multi-region

App Passed Failed Skipped
✅ nextjs-turbopack 27 0 0

📋 View full workflow run

@github-actions

github-actions Bot commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

📊 Workflow Benchmarks

commit de1d17f · Fri, 14 Aug 2026 18:53:33 GMT · run logs

Backend: vercel · app: nextjs-turbopack

Metric Scenario Best (ms) P75 (ms) P90 (ms) P99 (ms) Samples
TTFS step 475 (-56%) 💚 1473 🔴 (+2.4%) 1487 🔴 (-1.5%) 1710 🔴 (+5.4%) 30
TTFS stream 1411 (+175%) 🔻 1467 🔴 (+13%) 1479 🔴 (+13%) 1505 🔴 (+6.6%) 30
TTFS hook + stream 545 (-12%) 1794 🔴 (+8.9%) 1907 🔴 (+8.0%) 1955 🔴 (+0.5%) 30
Fan-out TTFS Promise.all(100 steps) 8913 (±0%) 10485 (+4.5%) 10604 (+4.2%) 10705 (+3.9%) 10
Fan-out TTLS Promise.all(100 steps) 17535 (+0.7%) 19203 (+1.6%) 19356 (+2.0%) 20686 (+2.8%) 10
STSO 1020 steps (inline) 132 (-5.7%) 173 (-25%) 💚 195 (-30%) 💚 328 (-56%) 💚 1019
WO 1020 steps 172912 (-24%) 💚 172912 (-24%) 💚 172912 (-24%) 💚 172912 (-24%) 💚 1
SL stream latency 87 (-26%) 💚 124 🔴 (-32%) 💚 158 🔴 (-34%) 💚 444 🔴 (-36%) 💚 30
SO stream overhead (text) 94 (-31%) 💚 177 (-25%) 💚 198 (-34%) 💚 249 (-56%) 💚 30
SO stream overhead (structured) 109 (-26%) 💚 176 (-33%) 💚 216 (-26%) 💚 3255 🔴 (+686%) 🔻 30
📈 STSO distribution vs main (inline / queue-hop histograms)

1020 steps (inline)

Cumulative STSO time: main 226900ms → this run 172717ms (Δ -54183ms, -24%)

  100-150 ms  █░░░░░┃                   main  11  this 204  +193
  150-200 ms  ████████████████░░░░░░░┃  main 499  this 730  +231
  200-250 ms  █┃█████████               main 338  this  51  -287
  250-300 ms  ┃██                       main  90  this  16   -74
  300-350 ms  ┃                         main  27  this  10   -17
  350-400 ms  ┃                         main  20  this   2   -18
  400-450 ms  ┃                         main   5  this   2    -3
  450-500 ms  ┃                         main   4  this   1    -3
  500-550 ms  ┃                         main   3  this   0    -3
  550-600 ms  ┃                         main   0  this   1    +1
  600-650 ms  ┃                         main   1  this   1    +0
  650-700 ms  ┃                         main   5  this   0    -5
  700-750 ms  ┃                         main   8  this   1    -7
  800-850 ms  ┃                         main   2  this   0    -2
  850-900 ms  ┃                         main   2  this   0    -2
  900-950 ms  ┃                         main   2  this   0    -2
1050-1100 ms  ┃                         main   1  this   0    -1
1150-1200 ms  ┃                         main   1  this   0    -1
ℹ️ Metric definitions & methodology

The collapsed STSO distribution section above buckets every step gap of the sequential-steps run (not a sampled window), split by whether the step ending the gap ran inline — in the same warm process as the step before it, so the gap is pure framework overhead — or after a queue-hop — the first step of a fresh process, which pays queue dispatch, client reinit and event-log replay. Bars overlay the two runs: is main, marks where this run lands, bridges the gap when this run has more samples in a bucket.

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, deployment clocks) · 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) · SL: stream latency (in-deployment write → read propagation, readAt - writtenAt) · SO: stream overhead (end-to-end write+consume time beyond the modelled generation window)

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 · stream latency: parallel reader/writer steps on a dedicated stream; SL is the in-deployment write->read propagation (readAt - writtenAt) · stream overhead (text): writer streams 300 variable-length text token deltas paced at 100/s for 3s (a haiku-size LLM's token throughput) while a parallel reader drains the whole stream; SO is the end-to-end write+consume time beyond the 3s generation window (overhead/backpressure) · stream overhead (structured): same workload as stream overhead (text), but each delta is an AI-SDK-style structured object ({ type: 'text-delta', id, text }) instead of a raw string, so the SO gap vs the text scenario is the added serialization cost

🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · SO 250/500/1000

All metrics are measured from deployment-side timestamps only. Runs are triggered by an in-deployment route that stamps the anchor (clientStart) right before start(), so the CI runner’s request and its path through api.vercel.com sit outside every measured window. TTFS = in-deployment start() → first step body (turbo uses the in-process fast path, non-turbo the dispatch path), and includes the VQS dispatch hop plus any /flow cold start. Fan-out TTFS/TTLS are the first and last step completions of a single Promise.all over trivial steps, from the same anchor, so the gap between the two rows is the spread the runtime adds across the fan-out. STSO/WO are measured between step bodies on the deployment. SL is measured inside the workflow (parallel reader/writer steps), so it no longer includes the api.vercel.com read path.

Cold starts are kept in the numbers on purpose — they are part of real bursty-workload latency. The workbench deployment cold-starts the /flow invocation for a large fraction of runs, inflating P75+; the Best column shows the fastest (warm-start) sample for comparison.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Updates the CI “Next.js canary” E2E lanes to a newer Next.js canary while ensuring pnpm’s minimumReleaseAge gate doesn’t block installs of freshly published canary artifacts.

Changes:

  • Bump the canary pin used by the local E2E jobs from 16.3.0-canary.2 to 16.3.1-canary.17.
  • Add next and @next/* to pnpm’s minimumReleaseAgeExclude so CI can install new canaries without ERR_PNPM_NO_MATURE_MATCHING_VERSION.

Reviewed changes

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

File Description
pnpm-workspace.yaml Excludes next / @next/* from the minimum release-age gate to allow fresh canary installs in CI.
.github/workflows/tests.yml Updates the hardcoded canary pin used in the canary setup step across the local E2E jobs.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@github-actions

Copy link
Copy Markdown
Contributor

Sim World

Simulated world deterministic testing for races. Traces

🟠 Mint-ordered log — 3 fail of 41 total

log=mint-ordered · 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
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 failed 9 1.0m MISMATCH 1
in-flight-before-decision-counted failed 9 1.0m MISMATCH 1
in-flight-after-decision failed 9 1.0m MISMATCH 1
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-mint.txt

🟢 Append-only log — 0 fail of 41 total

log=append-only · 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
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-append-only.txt

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.

4 participants