| Bug #47449 | main.information_schema and innodb.innodb_information_schema fail sporadically | ||
|---|---|---|---|
| Submitted: | 19 Sep 2009 9:33 | Modified: | 30 Jun 2011 15:09 |
| Reporter: | Alexander Nozdrin | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | MySQL Server: Tests | Severity: | S3 (Non-critical) |
| Version: | OS: | Any | |
| Assigned to: | Anitha Gopi | CPU Architecture: | Any |
| Tags: | experimental, pb2, sporadic, test failuyre | ||
[19 Sep 2009 9:33]
Alexander Nozdrin
[21 Sep 2009 7:45]
Sveta Smirnova
Thank you for the report.
Verified as log was provided.
Test failure reason:
main.information_schema w6 [ fail ] timeout after 900 seconds
Test ended at 2009-09-17 20:55:20
Test case timeout after 900 seconds
[7 Jul 2010 11:33]
Georgi Kodinov
I don't think this is related to information_schema test. Most probably some pb2 or platform oddity.
[8 Jul 2010 4:45]
Anitha Gopi
The failure reason is different in http://pb2.norway.sun.com/web.py?template=mysql_show_test_failure&test_failure_id=2328369&...;... CURRENT_TEST: main.information_schema --- /Volumes/hd2/test/sb_1-2024718-1278530308.07/mysql-5.6.99-m4-osx10.5-x86-test/mysql-test/r/information_schema.result 2010-07-07 15:47:48.000000000 +0300 +++ /Volumes/hd2/test/sb_1-2024718-1278530308.07/mysql-5.6.99-m4-osx10.5-x86-test/mysql-test/r/information_schema.reject 2010-07-07 22:38:20.000000000 +0300 @@ -1248,7 +1248,7 @@ WHERE table_name=(SELECT MAX(table_name) FROM information_schema.tables WHERE table_schema IN ('mysql', 'INFORMATION_SCHEMA', 'test')); table_name -VIEWS +views DROP TABLE IF EXISTS bug23037; DROP FUNCTION IF EXISTS get_value; SELECT COLUMN_NAME, MD5(COLUMN_DEFAULT), LENGTH(COLUMN_DEFAULT) FROM INFORMATION_SCHEMA.COLUMNS WHERE TABLE_NAME='bug23037'; Should the test be made case insensitive
[17 Jan 2011 9:13]
Anitha Gopi
The original problem reported in this bug is not seen anymore. The last failure for innodb.innodb_information_schema was on mysql-trunk-bugfixing 0n 21/14/2010 http://pb2.norway.sun.com/web.py?template=mysql_show_test_failure&test_failure_id=3438002 innodb.innodb_information_schema [ exp-fail ] Test ended at 2010-12-14 23:03:42 CURRENT_TEST: innodb.innodb_information_schema InnoDB: !!!!!!!! UNIV_DEBUG switched on !!!!!!!!! InnoDB: The InnoDB memory heap is disabled InnoDB: Mutexes and rw_locks use GCC atomic builtins InnoDB: Compressed tables use zlib 1.2.3 101215 1:03:40 InnoDB: Initializing buffer pool, size = 8.0M 101215 1:03:40 InnoDB: Completed initialization of buffer pool 101215 1:03:40 InnoDB: highest supported file format is Barracuda. 101215 1:03:42 InnoDB: Assertion failure in thread 47866079053200 in file /export/home2/pb2/build/sb_1-None-1292337842.65/mysql-trunk-bugfixing-gcov/storage/innobase/trx/trx0i_s.c line 446 InnoDB: Failing assertion: row->lock_data != ((void *)0) InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: about forcing recovery. mysqltest got signal 6 read_command_buf (0x17642a0): let $success= `$wait_condition`, c10) ) conn->name (0xbc75e70): con_verify_innodb_locks conn->cur_query ((nil)): Attempting backtrace... stack_bottom = (nil) thread_stack 0x40000 The last failure for main.information_schema was on 21/12 http://pb2.norway.sun.com/web.py?template=mysql_show_test_failure&test_failure_id=3457605 The test is running fine on mysql-trunk for the past few weeks. It is better to enable these tests. Otherwise we are missing out on the new problems
[18 Jan 2011 17:48]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/129101 3229 Anitha Gopi 2011-01-18 Bug#47449: This problem not seen in PB2. Remove from experimental group
[18 Jan 2011 17:54]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/129102 3529 Anitha Gopi 2011-01-18 [merge] Bug#47449: Merge revision 3263 from mysql-5.5
[18 Jan 2011 18:05]
Bugs System
Pushed into mysql-trunk 5.6.2 (revid:anitha.gopi@sun.com-20110118175248-rz1c2wcc5scmu0a6) (version source revid:anitha.gopi@sun.com-20110118175248-rz1c2wcc5scmu0a6) (merge vers: 5.6.2) (pib:24)
[19 Jan 2011 1:22]
Bugs System
Pushed into mysql-5.5 5.5.10 (revid:anitha.gopi@sun.com-20110118180302-bko13mi9atvl4219) (version source revid:anitha.gopi@sun.com-20110118175139-9q215o3h47ospiks) (merge vers: 5.5.10) (pib:24)
