[MDEV-15095] parts.partition_debug_innodb failed in buildbot with "table doesn't exist" Created: 2018-01-27  Updated: 2018-07-12  Resolved: 2018-07-12

Status: Closed
Project: MariaDB Server
Component/s: Partitioning, Tests
Affects Version/s: 5.5
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None


 Description   

(with ps protocol)
http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2/builds/11111/steps/mtr_ps/logs/stdio

parts.partition_debug_innodb 'xtradb'    w4 [ fail ]
        Test ended at 2018-01-11 19:38:03
 
CURRENT_TEST: parts.partition_debug_innodb
mysqltest: In included file "./suite/parts/inc/partition_crash.inc": 
included from ./suite/parts/inc/partition_crash_drop.inc at line 12:
included from ./suite/parts/inc/partition_mgm_crash.inc at line 27:
included from /mnt/buildbot/build/mariadb-5.5.59/mysql-test/suite/parts/t/partition_debug_innodb.test at line 63:
At line 25: query 'SHOW CREATE TABLE t1' failed: 1146: Table 'test.t1' doesn't exist
 
The result from queries just before the failure was:
< snip >
13	Original from partition p1
14	Original from partition p1
2	Original from partition p0
3	Original from partition p0
4	Original from partition p0
ALTER TABLE t1 DROP PARTITION p10;
ERROR HY000: Lost connection to MySQL server during query
# State after crash (before recovery)
#sql-t1.frm
#sql-t1.par
t1#P#p0.ibd
t1#P#p10.ibd
t1.frm
t1.par
# State after crash recovery
t1#P#p0.ibd
t1#P#p10.ibd
t1.frm
t1.par
SHOW CREATE TABLE t1;
 
More results from queries before failure can be found in /mnt/buildbot/build/mariadb-5.5.59/mysql-test/var/4/log/partition_debug_innodb.log
 
 - saving '/mnt/buildbot/build/mariadb-5.5.59/mysql-test/var/4/log/parts.partition_debug_innodb-xtradb/' to '/mnt/buildbot/build/mariadb-5.5.59/mysql-test/var/log/parts.partition_debug_innodb-xtradb/'
 
Retrying test parts.partition_debug_innodb, attempt(2/3)...
 
worker[4] > Restart  - not started
***Warnings generated in error logs during shutdown after running tests: parts.partition_debug_innodb
 
dispatch_command: query: call mtr.add_suppression("InnoDB: Warning: allocated tablespace .*, old maximum was")
THD::decide_logging_format: info: Query: call mtr.add_suppression("InnoDB: Warning: allocated tablespace .*, old maximum was")
THD::decide_logging_format: info: Query: call mtr.add_suppression("InnoDB: Warning: allocated tablespace .*, old maximum was")
THD::decide_logging_format: info: Query: INSERT INTO test_suppressions (pattern) VALUES ( NAME_CONST('pattern',_latin1'InnoDB: Warning: allocated tablespace .*, old maximum was' COLLATE 'latin1_swedish_ci'))
THD::decide_logging_format: info: Query: INSERT INTO test_suppressions (pattern) VALUES ( NAME_CONST('pattern',_latin1'InnoDB: Warning: allocated tablespace .*, old maximum was' COLLATE 'latin1_swedish_ci'))
dispatch_command: query: call mtr.add_suppression("InnoDB: Error: table .* does not exist in the InnoDB internal")
THD::decide_logging_format: info: Query: call mtr.add_suppression("InnoDB: Error: table .* does not exist in the InnoDB internal")
THD::decide_logging_format: info: Query: INSERT INTO test_suppressions (pattern) VALUES ( NAME_CONST('pattern',_latin1'InnoDB: Error: table .* does not exist in the InnoDB internal' COLLATE 'latin1_swedish_ci'))
THD::decide_logging_format: info: Query: INSERT INTO test_suppressions (pattern) VALUES ( NAME_CONST('pattern',_latin1'InnoDB: Error: table .* does not exist in the InnoDB internal' COLLATE 'latin1_swedish_ci'))
dispatch_command: query: call mtr.add_suppression("InnoDB: Warning: MySQL is trying to drop table ")
THD::decide_logging_format: info: Query: call mtr.add_suppression("InnoDB: Warning: MySQL is trying to drop table ")
THD::decide_logging_format: info: Query: INSERT INTO test_suppressions (pattern) VALUES ( NAME_CONST('pattern',_latin1'InnoDB: Warning: MySQL is trying to drop table ' COLLATE 'latin1_swedish_ci'))
THD::decide_logging_format: info: Query: INSERT INTO test_suppressions (pattern) VALUES ( NAME_CONST('pattern',_latin1'InnoDB: Warning: MySQL is trying to drop table ' COLLATE 'latin1_swedish_ci'))
dispatch_command: query: call mtr.add_suppression("Attempting backtrace. You can use the following information to find out")
THD::decide_logging_format: info: Query: call mtr.add_suppression("Attempting backtrace. You can use the following information to find out")
THD::decide_logging_format: info: Query: INSERT INTO test_suppressions (pattern) VALUES ( NAME_CONST('pattern',_latin1'Attempting backtrace. You can use the following information to find out' COLLATE 'latin1_swedish_ci'))
THD::decide_logging_format: info: Query: INSERT INTO test_suppressions (pattern) VALUES ( NAME_CONST('pattern',_latin1'Attempting backtrace. You can use the following information to find out' COLLATE 'latin1_swedish_ci'))
InnoDB: Error: trying to load index GEN_CLUST_INDEX for table test/t1#P#p10
180111 19:38:03 [ERROR] Failed to open table test/t1#P#p10.
180111 19:38:03 [ERROR] Cannot find or open table test/t1#P#p10 from



 Comments   
Comment by Elena Stepanova [ 2018-07-12 ]

It only happened on 5.5, and only once in the recorded buildbot history. Closing, since we are not fixing 5.5-only bugs anymore. If it happens on a later version, we'll re-open it or create a new one.

Generated at Thu Feb 08 08:18:39 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.