From 467aa0a87d4b52521cd262ba4dc3393fe7951482 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Matheus=20Vila=C3=A7a=20de=20Jesus?= Date: Sun, 25 Oct 2026 18:36:04 -0300 Subject: [PATCH 1/2] chore: start #636 From 286f5d865cb9b701549adf31bb57369532639dc9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Matheus=20Vila=C3=A7a=20de=20Jesus?= Date: Sun, 25 Oct 2026 18:36:18 -0300 Subject: [PATCH 2/2] docs: 4.6.0 post states the dev-tooling targets that were not met (#636) --- site/src/content/changelog/4.6.0.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/site/src/content/changelog/4.6.0.mdx b/site/src/content/changelog/4.6.0.mdx index 349bfc3f..c7e1d5af 100644 --- a/site/src/content/changelog/4.6.0.mdx +++ b/site/src/content/changelog/4.6.0.mdx @@ -312,6 +312,8 @@ Every command has a time budget that is enforced: a run over its budget fails an Later work held the land gate under its budget: with a shared change (every component test, 210 files) it measured 224.8 s with a cold social-card cache and 193.5 s with a warm one, at load 7 on 12 cores, against a 240 s budget (pull request 599). `bun run test:full` has a 300 s budget and, by the record in that same pull request, was not measured on a quiet machine: one run took 1092 s at load 50 and is not a result. We state it so you do not read the budget as a promise. +Three dev-tooling targets were not met in this release. A shared-change land (every component test) took 255 s against a 120 s target. Our own tooling peaks at 8 cores in one land against a 4-core cap, and that cap is not enforced yet (issue 632). The warm `bun run test` still takes 11 to 13 s against a 10 s target. The enforced budgets above hold; these targets are what we are still working toward, and the numbers are wall time on the maintainer's shared 12-core machine. +