Repository navigation
Conversation
page-errors, server-auth-errors and http-errors-playground each ran every variant (framework, sign-in state, dev/production) one after another in one file, so each held a worker for 50-67 seconds. The suite body now lives in a *-suite.ts module and one small test file per variant calls it, so the variants run in parallel workers. Every test still runs, with its own fixture copy and server as before. Measured alone on a 12-core M4 Pro: page-errors 67s -> 4 files, longest 18s server-auth-errors 52s -> 3 files, longest 21s http-errors-playground 68s -> 2 files, longest 26s Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
cf-version-runner, cf-build-output, cf-version-transport and cloudflare-operation-process spend their time waiting for real child processes, one test at a time. Their tests now run concurrently (Vitest's default of five at once). Each test already has its own temporary directory and local API server. To make that safe: - Tests that use `vi` stay serial through `serialIt`. They patch globals, and Vitest clears every mock's call history when another test starts. - Shared cleanup lists are drained when the file ends, not after each test. - Tests read their own project root with `outputRoot(prepared)` instead of the last entry of the shared `roots` list. - The cloudflare-operation-process files join the cli-unit project, which gets a 20-second test timeout on every platform: a test now also waits while its neighbours block the thread in a synchronous spawn. Measured alone on a 12-core M4 Pro: cloudflare-operation-process 31s -> 5s cf-version-runner 44s -> 22s cf-build-output 22s -> 11s cf-version-transport 18s -> 6s Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
`vp run --cache build:all` reran packages/platform's runtime build (about 6 seconds) on every invocation. The build empties dist/runtime before writing it, which the task cache records as reading those files, and the uncached `build:stamp` step then edits the manifest in that directory. The runtime build's own output therefore always looked like a changed input. The step is now a `build:runtime` task that excludes dist/runtime from its inputs. Its real inputs (sources, the API build, migrations) are still tracked automatically. Measured on a 12-core M4 Pro, `vp run --cache build:all` with nothing changed: 14s -> 8s. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…timates The split browser files had no entry in the timing table, so the longest-first sequencer and the CI shard balancer treated each as a 5s file. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
🚀 Deploying Preview to Cloudflare 🚀Preview URL: https://test-speed-void-cloud.voidzero-docs.workers.dev (commit 246d1c9)This URL reflects your latest Preview deploymentPreview Deployments by commit
|
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Draft opened only to observe CI timing for the
test-speedbranch; not ready for review.cfsubprocess unit tests concurrently within each file.TESTING.mdnotes for the above.Local
vpr test:all(M4 Pro, warm build cache): 248s → 193s.🤖 Generated with Claude Code