main.signal_demo3 fails in buildbot on labrador

main.signal_demo3                        [ fail ]

        Test ended at 2017-01-03 21:37:10

CURRENT_TEST: main.signal_demo3

mysqltest: At line 107: query 'call proc_1()' failed with wrong errno 1051: 'Unknown table 'demo.oops_it_is_not_here'', instead of 1644...

The result from queries just before the failure was:

< snip >

resignal sqlstate '45000' set message_text='Oops in proc_7';

call proc_8();

end

$$

create procedure proc_8()

begin

declare exit handler for sqlexception

resignal sqlstate '45000' set message_text='Oops in proc_8';

call proc_9();

end

$$

create procedure proc_9()

begin

declare exit handler for sqlexception

resignal sqlstate '45000' set message_text='Oops in proc_9';

## Do something that fails, to see how errors are reported

drop table oops_it_is_not_here;

end

$$

call proc_1();

main.signal_demo3                        [ fail ]

        Test ended at 2017-01-04 18:21:11

CURRENT_TEST: main.signal_demo3

mysqltest: At line 107: query 'call proc_1()' failed with wrong errno 1436: 'Thread stack overrun:  186352 bytes used of a 297984 byte stack, and 112000 bytes needed.  Use 'mysqld --thread_stack=#' to specify a bigger stack', instead of 1644...

The result from queries just before the failure was:

< snip >

resignal sqlstate '45000' set message_text='Oops in proc_7';

call proc_8();

end

$$

create procedure proc_8()

begin

declare exit handler for sqlexception

resignal sqlstate '45000' set message_text='Oops in proc_8';

call proc_9();

end

$$

create procedure proc_9()

begin

declare exit handler for sqlexception

resignal sqlstate '45000' set message_text='Oops in proc_9';

## Do something that fails, to see how errors are reported

drop table oops_it_is_not_here;

end

$$

call proc_1();

More results from queries before failure can be found in /Users/mariadb/elenst/bb-10.2-serg/mysql-test/var/log/signal_demo3.log