MySQL Bugs: #39855: innodb_mysql fails sporadically with assert in pushbuild (rpl trees, embedded)

Bug #39855	innodb_mysql fails sporadically with assert in pushbuild (rpl trees, embedded)
Submitted:	4 Oct 2008 11:23	Modified:	2 May 2009 17:29
Reporter:	Sven Sandberg	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Tests	Severity:	S7 (Test Cases)
Version:	5.1-rpl	OS:	Any
Assigned to:	Assigned Account	CPU Architecture:	Any
Tags:	assert, innodb_mysql, pushbuild, sporadic, test failure

Description:
pushbuild says:

main.innodb_mysql                        [ fail ]

CURRENT_TEST: main.innodb_mysql
InnoDB: The first specified data file /dev/shm/var-embedded-110/1/mysqld.1/data/ibdata1 did not exist:
InnoDB: a new database to be created!
080916  9:19:44  InnoDB: Setting file /dev/shm/var-embedded-110/1/mysqld.1/data/ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
080916  9:19:44  InnoDB: Log file /dev/shm/var-embedded-110/1/mysqld.1/data/ib_logfile0 did not exist: new to be created
InnoDB: Setting log file /dev/shm/var-embedded-110/1/mysqld.1/data/ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
080916  9:19:44  InnoDB: Log file /dev/shm/var-embedded-110/1/mysqld.1/data/ib_logfile1 did not exist: new to be created
InnoDB: Setting log file /dev/shm/var-embedded-110/1/mysqld.1/data/ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
080916  9:20:27  InnoDB: Error: table `test`.`bug29807` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting.html
mysqltest_embedded: protocol.cc:437: void net_end_statement(THD*): Assertion `! thd->main_da.is_sent' failed.
mysqltest got signal 6
read_command_buf at 0x8c994e0 = disconnect con2
conn->name at 0x9bce888 = 
conn->cur_query at (nil) is an invalid pointer
Attempting backtrace...
stack_bottom = (nil) thread_stack 0x30c00
/data0/pushbuild/pb2/pb/bzr_mysql-6.0-rpl/72/mysql-6.0.8-alpha-pb72/libmysqld/examples/mysqltest_embedded(my_print_stacktrace+0x26)[0x825658b]
/data0/pushbuild/pb2/pb/bzr_mysql-6.0-rpl/72/mysql-6.0.8-alpha-pb72/libmysqld/examples/mysqltest_embedded[0x81fd414]
/data0/pushbuild/pb2/pb/bzr_mysql-6.0-rpl/72/mysql-6.0.8-alpha-pb72/libmysqld/examples/mysqltest_embedded[0x81fd43e]
[0xffffe420]
/lib/tls/libc.so.6(abort+0x109)[0x401bf0c9]
/lib/tls/libc.so.6(__assert_fail+0x10f)[0x401b705f]
/data0/pushbuild/pb2/pb/bzr_mysql-6.0-rpl/72/mysql-6.0.8-alpha-pb72/libmysqld/examples/mysqltest_embedded(_Z17net_end_statementP3THD+0x5e)[0x8262b34]
/data0/pushbuild/pb2/pb/bzr_mysql-6.0-rpl/72/mysql-6.0.8-alpha-pb72/libmysqld/examples/mysqltest_embedded(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1492)[0x82f9696]
/data0/pushbuild/pb2/pb/bzr_mysql-6.0-rpl/72/mysql-6.0.8-alpha-pb72/libmysqld/examples/mysqltest_embedded[0x821e153]
/data0/pushbuild/pb2/pb/bzr_mysql-6.0-rpl/72/mysql-6.0.8-alpha-pb72/libmysqld/examples/mysqltest_embedded(mysql_send_query+0x86)[0x8210a5e]
/data0/pushbuild/pb2/pb/bzr_mysql-6.0-rpl/72/mysql-6.0.8-alpha-pb72/libmysqld/examples/mysqltest_embedded(send_one_query+0x38)[0x820b786]
/lib/tls/libpthread.so.0[0x4010b0bd]
/lib/tls/libc.so.6(__clone+0x5e)[0x402609ee]

 - saving '/dev/shm/var-embedded-110/1/log/main.innodb_mysql/' to '/dev/shm/var-embedded-110/log/main.innodb_mysql/'

Retrying test, attempt(2/3)...

How to repeat:
https://intranet.mysql.com/secure/pushbuild/showpush.pl?dir=bzr_mysql-6.0-rpl&order=72 debx86-b/embedded
xref: http://tinyurl.com/4qfdkb

Thank you for the bug report.

I have two questions:

a- when (as in bzr revno) do you think it started?
b- do you have a numerical estimate on 'sporadically'? Does it fail in every other run, or at a rate of something like 5-10%, for example?

As seen in the xref link in "how to reproduce", this has only happened twice (as of 2008-10-21), both times in the middle of September 2008. So it happens seldom, and it's difficult to say which push it was introduced (probably between 0 and 20 pushes before the ones where it failed).

1. It hasn't happened in PB1 since 2008-Sep-15.
2. I can't reproduce it even under high load.

So, I'm moving it to 'Need Feedback'. If it does not reappear
in a month, the bug will be closed.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".