From a719444f68c7448f53ce61dc9f02e552a98fedcf Mon Sep 17 00:00:00 2001 From: Andrew Tridgell Date: Sun, 15 Oct 2006 21:42:45 +0000 Subject: r19298: make sure torture_fail() gives a useful message Jelmer, is there a better approach for this? (This used to be commit 67e2cf921709e0833362cb3b1bd5558f3c359033) --- source4/torture/ui.c | 2 ++ 1 file changed, 2 insertions(+) (limited to 'source4/torture') diff --git a/source4/torture/ui.c b/source4/torture/ui.c index 50bb2482d7..4abc3339d4 100644 --- a/source4/torture/ui.c +++ b/source4/torture/ui.c @@ -45,6 +45,8 @@ void torture_fail(struct torture_context *context, const char *fmt, ...) va_start(ap, fmt); context->last_reason = talloc_vasprintf(context, fmt, ap); + /* make sure the reason for the failure is displayed */ + context->ui_ops->comment(context, context->last_reason); va_end(ap); context->last_result = TORTURE_FAIL; } -- cgit