From 40f4b8e5acfa77f32372dff3c6e738905c59d0de Mon Sep 17 00:00:00 2001 From: Johnathan Corgan Date: Sat, 15 Aug 2026 08:25:12 +0000 Subject: [PATCH] Count the new path-MTU purge step in the profiler row-count guard The merge added an unconditional tick step, purge_expired_path_mtu, which took the emitted subsystem steps from 24 to 25. The pinned row count is only compiled under the profiling feature, so the ordinary four-check run did not see it and local CI caught it in the profiling suite. The guard did its job: it exists so the step table and its expected size cannot diverge unnoticed. Re-checked by setting the count one too high and confirming it fails. --- src/instr/recorder.rs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/instr/recorder.rs b/src/instr/recorder.rs index 7addb7f1..92ee913d 100644 --- a/src/instr/recorder.rs +++ b/src/instr/recorder.rs @@ -378,9 +378,9 @@ mod tests { #[test] fn emitted_row_count_matches_build() { let emitted = STEPS.iter().filter(|s| s.emitted()).count(); - // 24 unconditional subsystem steps + the whole-tick span, plus the two + // 25 unconditional subsystem steps + the whole-tick span, plus the two // conditionally-compiled steps where this build has them. - let mut expected = 25; + let mut expected = 26; if cfg!(any(target_os = "linux", target_os = "macos")) { expected += 1; }