Skip to content

The fastest, cheapest, most efficient open-source agent harness. Run more than 500 agents on a $10 VPS.

test(triage): remove debug error logging from escalation tests

Steven Enamakel36aca1ce14ef
diff --git a/crates/openhuman-core/src/triage/escalation_model_tests.rs b/crates/openhuman-core/src/triage/escalation_model_tests.rs
index 608a2025b9..66bf72e660 100644
--- a/crates/openhuman-core/src/triage/escalation_model_tests.rs
+++ b/crates/openhuman-core/src/triage/escalation_model_tests.rs
@@ -147,7 +147,7 @@ async fn react_dispatch_keeps_routing_without_creating_child_lifecycle_records()
),
)
.await
- .inspect_err(|e| eprintln!("DBGERR {e:?}")).expect("react escalation should complete");
+ .expect("react escalation should complete");
// Prove that the requested route reached the model before checking the
// lifecycle boundary below, so a skipped dispatch cannot satisfy it.
@@ -399,7 +399,7 @@ async fn react_dispatch_falls_back_to_parent_model_when_hint_route_cannot_build(
),
)
.await
- .inspect_err(|e| eprintln!("DBGERR {e:?}")).expect("react escalation should complete");
+ .expect("react escalation should complete");
let builds = builds.lock().unwrap();
assert!(builds.iter().any(|(role, _)| role == "chat"));