a fresh clone gets the whole project, and the maintainer's tooling moves out
What a clone lacked: the gates went green with a thousand skipped tests and said nothing, every login script assumed a worktree-pool slot and its probe account, the client defaulted to the maintainer's account, a docker path and a home directory were in the code, the temp files broke on GNU coreutils, and two generators could only run against a sibling repo. Now the test gates print how many data-gated tests skipped and why; a scripted run logs in as the account its checkout declares in `.probe-identity` or as the three variables name, never a default, and the client refuses a scripted login on any other account; the event and message tables regenerate from vendored inputs, byte for byte; the docs state the real prerequisites. Out of the tree, into the maintainer's own tooling: the worktree pool, its hooks, the perf leg runner, the cross-platform compile and the Vulkan container leg — a way of working, and setups not every machine has. One hook stays: no writes into the install. Two tests that could never run are gone with their subject: the quest-timer geometry diff compared a copy of the window that no longer exists (and joined a chain path onto a folder, so it always skipped), and the FrameXML flag gate now reads the stock files off the player's own patch chain instead of an extracted folder only one machine had. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
@@ -47,7 +47,7 @@ fn dispatch_bench() {
|
||||
// A plain Lua table with a table `__index` — the floor this path could reach, and what the
|
||||
// reference client's flat `{name, lua_CFunction}` probe costs in C.
|
||||
// **The MINIMUM of [`ROUNDS`] runs, never the mean.** This machine builds while it measures —
|
||||
// a neighbouring worktree's `cargo` saturates ten cores — and a mean of a contended loop reads
|
||||
// another build on the same machine saturates ten cores — and a mean of a contended loop reads
|
||||
// whatever else was running. The minimum is the closest thing to the uncontended cost that a
|
||||
// shared machine can report, and it is what makes two rows of one run comparable at all.
|
||||
let floor = |what: &str, chunk: &str| {
|
||||
|
||||
Reference in New Issue
Block a user