From 28f31a4f8da9367a950e89f28a4ec2314d0e48e0 Mon Sep 17 00:00:00 2001 From: Nick Mathewson Date: Fri, 6 Aug 2010 16:36:23 -0400 Subject: [PATCH] Fix unit tests with -DUSE_DEBUG enabled If you were to enable USE_DEBUG and slog through all 700+ MB of debugging output, you'd find that one of the unit tests failed, since it tested the debug logging code, but the string it expected and the string it logged differed by a tab vs 2 spaces. --- test/regress_util.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/test/regress_util.c b/test/regress_util.c index acfdf91b..47b5cbfd 100644 --- a/test/regress_util.c +++ b/test/regress_util.c @@ -525,9 +525,9 @@ test_evutil_log(void *ptr) LOGEQ(_EVENT_LOG_MSG, "Connecting lime to coconut"); RESET(); - event_debug(("A millisecond passed! We should log that!")); + event_debug(("A millisecond passed! We should log that!")); #ifdef USE_DEBUG - LOGEQ(_EVENT_LOG_DEBUG, "A millisecond passed! We should log that!"); + LOGEQ(_EVENT_LOG_DEBUG, "A millisecond passed! We should log that!"); #else tt_int_op(logsev,==,0); tt_ptr_op(logmsg,==,NULL);