From 542892f8e9370582f40a4e1528a7ff01bb004dd3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ralph=20K=C3=BCpper?= Date: Sat, 13 Jun 2026 23:17:51 +0200 Subject: [PATCH] test(node-suite): normalize env-variant tokens so console scores 119/119 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The console formatter already matches node v26 byte-for-byte on every deterministic output across all 119 node-suite console tests. The 10 residual diffs were entirely environment-variant content that the print-and-diff runner compared raw: - 9x console.time/timeEnd/timeLog: node's formatTime prints a live hrtime delta as the raw float `${ms}ms`, non-deterministic run-to-run (node itself prints 0.004ms / 0.004ms / 0.003ms across three runs). - 1x output/error-cause: stack-trace frames (absolute paths, line/col, node-internal ESM-loader frames Perry can't reproduce). Masking ms / removing frame lines makes every one byte-identical, i.e. they were never Perry defects — they're the timing/stack class the suite docs already say to leave alone. Fix the scorer, not the runtime: node_suite_run.normalize() scrubs the two env-variant token classes symmetrically from both node and perry stdout before the equality check (mirrors gen_feature_matrix.py already stripping `(node:PID) Warning` noise): - durations: anchored on the `