[MDEV-14353] innodb.innodb-page_compression_lzma fails in buildbot on Fedora 25 Created: 2017-11-10  Updated: 2023-04-12  Resolved: 2023-04-11

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.1
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Jan Lindström (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None


 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-rpm-fedora25-x86/builds/1294/steps/mtr/logs/stdio

innodb.innodb-page_compression_lzma 'xtradb' w4 [ fail ]
 
        Test ended at 2017-11-10 11:41:07
 
 
 
CURRENT_TEST: innodb.innodb-page_compression_lzma
 
--- /usr/share/mysql-test/suite/innodb/r/innodb-page_compression_lzma.result	2017-11-10 09:23:52.000000000 +0000
 
+++ /dev/shm/var/4/log/innodb-page_compression_lzma.reject	2017-11-10 11:41:07.339958330 +0000
 
@@ -57,7 +57,7 @@
 
 # innodb_page_compressed8 page compressed expected NOT FOUND
 
 NOT FOUND /AaAaAaAa/ in innodb_page_compressed8.ibd
 
 # innodb_page_compressed9 page compressed expected NOT FOUND
 
-NOT FOUND /AaAaAaAa/ in innodb_page_compressed9.ibd
 
+FOUND /AaAaAaAa/ in innodb_page_compressed9.ibd
 
 select count(*) from innodb_page_compressed1;
 
 count(*)
 
 10000
 
 
 
mysqltest: Result length mismatch



 Comments   
Comment by Jan Lindström (Inactive) [ 2018-02-16 ]

commit d42c1a5534df5a3495ce927d7fd15debcf5fe577
Author: Jan Lindström <jan.lindstrom@mariadb.com>
Date: Fri Feb 16 14:15:55 2018 +0200

MDEV-14353: innodb.innodb-page_compression_lzma fails in buildbot on Fedora 25

Error 5 means that lzma failed to allocate required memory, moving
to big test.

Comment by Marko Mäkelä [ 2021-10-26 ]

The result difference could occur because some page flushing did not take place.

These tests could be made more deterministic by invoking FLUSH TABLES…FOR EXPORT. I am rather confident that starting with 10.5, thanks to MDEV-15528 and MDEV-8139, the implementation should be solid.

Comment by Jan Lindström [ 2023-04-11 ]

10.1 is EOL.

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