From ae393fd9ceb0a1adf7f817d67e36a1c00dac3cf8 Mon Sep 17 00:00:00 2001 From: jyviko <2501648+jyviko@users.noreply.github.com> Date: Wed, 28 Oct 2026 18:02:47 -0400 Subject: [PATCH] step_in tests: a face with too many bounds is refused by the reader's own limit The face-bounds limit lives in crates/step's topology (MAX_BOUNDS, 54b10b9a3) since the truck reader that said 'boundary loops' went (ab8bc6625); it names the face and its bound count. The test asserts that message; the time bound stays. Co-Authored-By: Claude Opus 5.5 --- crates/kernel/src/step_in/tests.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/crates/kernel/src/step_in/tests.rs b/crates/kernel/src/step_in/tests.rs index 5dfb386c4..ee10484d6 100644 --- a/crates/kernel/src/step_in/tests.rs +++ b/crates/kernel/src/step_in/tests.rs @@ -1540,7 +1540,7 @@ fn faces_with_too_many_bounds_are_refused() { let start = std::time::Instant::now(); let imp = step_import(&text).unwrap(); - assert!(imp.warnings.iter().any(|w| w.contains("boundary loops")), "{:?}", imp.warnings); + assert!(imp.warnings.iter().any(|w| w.contains("face #900000 with 100000 bounds")), "{:?}", imp.warnings); assert!(start.elapsed() < std::time::Duration::from_secs(10), "took {:?}", start.elapsed()); }