[MDEV-16111] [10.1] encryption.innodb_lotoftables failed in buildbot with wrong result Created: 2018-05-07  Updated: 2019-06-12  Resolved: 2019-06-12

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.1
Fix Version/s: 10.2.25, 10.1.41, 10.3.16, 10.4.6

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Marko Mäkelä
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-11531 encryption.innodb_lotoftables failed ... Closed

 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest-big/builds/1766

encryption.innodb_lotoftables 'innodb_plugin' w2 [ fail ]
        Test ended at 2018-04-30 17:01:01
 
CURRENT_TEST: encryption.innodb_lotoftables
--- /mnt/buildbot/build/mariadb-10.1.33/mysql-test/suite/encryption/r/innodb_lotoftables.result	2018-04-30 06:00:11.000000000 -0400
+++ /mnt/buildbot/build/mariadb-10.1.33/mysql-test/suite/encryption/r/innodb_lotoftables.reject	2018-04-30 17:01:00.845259421 -0400
@@ -923,6 +923,7 @@
 innodb_encrypted_3/t_99
 SELECT NAME FROM INFORMATION_SCHEMA.INNODB_TABLESPACES_ENCRYPTION WHERE MIN_KEY_VERSION <> 0 AND NAME LIKE 'innodb_encrypted%' ORDER BY NAME;
 NAME
+innodb_encrypted_1/t_68
 innodb_encrypted_2/t_1
 innodb_encrypted_2/t_10
 innodb_encrypted_2/t_100
@@ -1129,6 +1130,7 @@
 innodb_encrypted_2/t_99
 SELECT NAME FROM INFORMATION_SCHEMA.INNODB_TABLESPACES_ENCRYPTION WHERE MIN_KEY_VERSION = 0 AND NAME LIKE 'innodb_encrypted%' ORDER BY NAME;
 NAME
+innodb_encrypted_1/t_68
 innodb_encrypted_3/t_1
 innodb_encrypted_3/t_10
 innodb_encrypted_3/t_100
 
mysqltest: Result length mismatch

Apparently it was fixed in 10.2 in the scope of MDEV-11531, but 10.1 is still affected.



 Comments   
Comment by Marko Mäkelä [ 2019-06-12 ]

I removed the test, also from mysql-test/unstable-tests.

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