From: Bjorn Munch
Date: January 19 2011 9:53pm
Subject: Re: bzr commit into mysql-next-mr-bugfixing branch (guilhem.bichot:3260)
List-Archive: http://lists.mysql.com/commits/129237
Message-Id: <20110119215316.GA4132@moog.norway.sun.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On 19/01 21.14, Guilhem Bichot wrote:
>
> Maybe we could do a sql_print_warning() instead of DBUG_ASSERT(0); mtr 
> warns when it sees an unexpected warning, it marks the test as failed, 
> prints the warning on stderr, and returns 1 as exit code. I guess this 
> would be good enough?

I'm not familiar with all the context here, but just let me add a
comment from the perspective of mtr: yes, mtr will see an unexpected
warning in the server log and report the test as failed, but it has no
way of knowing what action from the test caused that warning. The test
will have run to its end.

If the server dies OTOH, test execution stops and mtr will also print
out the last statements executed before the crash.

- Bjorn