From 3c09a0f9e5c0332c637b8eacf09b12de8fb58cfb Mon Sep 17 00:00:00 2001 From: tannevaled Date: Fri, 21 Aug 2026 14:33:35 +0200 Subject: [PATCH] ruby/spec: raise the floor, 14200 -> 14900 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The floor had not moved while the total climbed under it: 14303 on 17 August, 14567 and 14625 on the 18th, and 14949-14963 now that the five memory blowups are fixed and five more spec files load. A floor 750 below the measurement tolerates a regression of 750 examples in silence, which is the one thing a ratchet exists not to do. Not pinned to the measurement, and I was wrong to propose that the first time. I argued the total was deterministic because two runs of one commit both said 14878. Two more runs of the same tree then said 14949 and 14963 — fourteen apart. Two samples agreeing is not determinism. 14900 is 49 below the lowest of those, which absorbs a jitter observed at 14, and 700 above where the floor sat. What would drop it much further is a heavy spec file failing to load, worth about 150 examples. That is now unlikely rather than routine: with the blowups fixed, the sweep's lowest free memory is 13.2 GB of 15, where a fortnight of runs died at 214 MB. If this lane ever reds by roughly 150, read "failed to load" in the log before looking for a conformance regression — it is 74 now, and was 79 before this week. --- scripts/conformance/rubyspec/FLOOR | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/conformance/rubyspec/FLOOR b/scripts/conformance/rubyspec/FLOOR index 753d1bf0..ce5f7acf 100644 --- a/scripts/conformance/rubyspec/FLOOR +++ b/scripts/conformance/rubyspec/FLOOR @@ -1 +1 @@ -14200 +14900