[MDEV-13891] innodb.101_compatibility failed in buildbot with wrong result Created: 2017-09-22  Updated: 2023-11-28

Status: Open
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.2, 11.1.1
Fix Version/s: 11.1

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None


 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-deb-wheezy-x86/builds/5231

innodb.101_compatibility '4k,innodb'     w4 [ fail ]
        Test ended at 2017-09-15 15:06:37
 
CURRENT_TEST: innodb.101_compatibility
--- /usr/share/mysql/mysql-test/suite/innodb/r/101_compatibility.result	2017-09-15 11:55:16.000000000 -0400
+++ /run/shm/var/4/log/101_compatibility.reject	2017-09-15 15:06:37.226876063 -0400
@@ -37,11 +37,18 @@
 test.ti	check	status	OK
 CHECK TABLE tr,tc,td,tz,tdd,tp,ti;
 Table	Op	Msg_type	Msg_text
-test.tr	check	status	OK
-test.tc	check	status	OK
-test.td	check	status	OK
-test.tz	check	status	OK
-test.tdd	check	status	OK
-test.tp	check	status	OK
-test.ti	check	status	OK
+test.tr	check	Error	Unknown storage engine 'InnoDB'
+test.tr	check	error	Corrupt
+test.tc	check	Error	Unknown storage engine 'InnoDB'
+test.tc	check	error	Corrupt
+test.td	check	Error	Unknown storage engine 'InnoDB'
+test.td	check	error	Corrupt
+test.tz	check	Error	Unknown storage engine 'InnoDB'
+test.tz	check	error	Corrupt
+test.tdd	check	Error	Unknown storage engine 'InnoDB'
+test.tdd	check	error	Corrupt
+test.tp	check	Error	Unknown storage engine 'InnoDB'
+test.tp	check	error	Corrupt
+test.ti	check	Error	Unknown storage engine 'InnoDB'
+test.ti	check	error	Corrupt
 DROP TABLE tr,tc,td,tz,tdd,tp,ti;
 
mysqltest: Result length mismatch



 Comments   
Comment by Timofey Turenko [ 2023-08-11 ]

another case:
https://mdbe-ci-repo.mariadb.net/bb-logs/MariaDBServerCommunityProduction/11.1.1/rhel_7_gcp/mtr-big-test/22921/

logs innodb.101_compatibility '8k,innodb'     w6 [ fail ]
        Test ended at 2023-08-10 20:40:35
 
CURRENT_TEST: innodb.101_compatibility
--- /usr/share/mariadb-test/suite/innodb/r/101_compatibility.result	2023-06-05 20:45:41.000000000 +0200
+++ /usr/share/mariadb-test/suite/innodb/r/101_compatibility.reject	2023-08-10 20:40:35.082411718 +0200
@@ -29,22 +29,36 @@
 # restart
 CHECK TABLE tr,tc,td,tz,tdd,tp,ti;
 Table	Op	Msg_type	Msg_text
-test.tr	check	status	OK
-test.tc	check	status	OK
-test.td	check	status	OK
-test.tz	check	status	OK
-test.tdd	check	status	OK
-test.tp	check	status	OK
-test.ti	check	status	OK
+test.tr	check	Error	Unknown storage engine 'InnoDB'
+test.tr	check	error	Corrupt
+test.tc	check	Error	Unknown storage engine 'InnoDB'
+test.tc	check	error	Corrupt
+test.td	check	Error	Unknown storage engine 'InnoDB'
+test.td	check	error	Corrupt
+test.tz	check	Error	Unknown storage engine 'InnoDB'
+test.tz	check	error	Corrupt
+test.tdd	check	Error	Unknown storage engine 'InnoDB'
+test.tdd	check	error	Corrupt
+test.tp	check	Error	Unknown storage engine 'InnoDB'
+test.tp	check	error	Corrupt
+test.ti	check	Error	Unknown storage engine 'InnoDB'
+test.ti	check	error	Corrupt
 # restart: --innodb-read-only
 CHECK TABLE tr,tc,td,tz,tdd,tp,ti;
 Table	Op	Msg_type	Msg_text
-test.tr	check	status	OK
-test.tc	check	status	OK
-test.td	check	status	OK
-test.tz	check	status	OK
-test.tdd	check	status	OK
-test.tp	check	status	OK
-test.ti	check	status	OK
+test.tr	check	Error	Unknown storage engine 'InnoDB'
+test.tr	check	error	Corrupt
+test.tc	check	Error	Unknown storage engine 'InnoDB'
+test.tc	check	error	Corrupt
+test.td	check	Error	Unknown storage engine 'InnoDB'
+test.td	check	error	Corrupt
+test.tz	check	Error	Unknown storage engine 'InnoDB'
+test.tz	check	error	Corrupt
+test.tdd	check	Error	Unknown storage engine 'InnoDB'
+test.tdd	check	error	Corrupt
+test.tp	check	Error	Unknown storage engine 'InnoDB'
+test.tp	check	error	Corrupt
+test.ti	check	Error	Unknown storage engine 'InnoDB'
+test.ti	check	error	Corrupt
 # restart
 DROP TABLE tr,tc,td,tz,tdd,tp,ti;
 
mysqltest: Result length mismatch
 
 - skipping '/var/tmp/mtr/6/log/innodb.101_compatibility-8k,innodb/'

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