From 5f478f5a9a58f72c0a844258b8ee614bf24ea9f7 Mon Sep 17 00:00:00 2001 From: Eric Wong Date: Fri, 17 Jun 2011 08:54:37 +0000 Subject: error logging is more consistent Backtraces are now formatted properly (with timestamps) and exceptions will be logged more consistently and similar to Logger defaults: "#{exc.message} (#{e.class})" backtrace.each { |line| ... } This may break some existing monitoring scripts, but errors will be more standardized and easier to check moving forward. --- t/t0001-reload-bad-config.sh | 1 + 1 file changed, 1 insertion(+) (limited to 't') diff --git a/t/t0001-reload-bad-config.sh b/t/t0001-reload-bad-config.sh index e1393ae..55bb355 100755 --- a/t/t0001-reload-bad-config.sh +++ b/t/t0001-reload-bad-config.sh @@ -34,6 +34,7 @@ t_begin "reload signal succeeds" && { done grep 'error reloading' $r_err >/dev/null + > $r_err } t_begin "hit with curl" && { -- cgit v1.2.3-24-ge0c7