[MDEV-14804] innodb.update_time failed in buildbot with wrong result Created: 2017-12-29  Updated: 2022-08-01  Resolved: 2022-08-01

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.2
Fix Version/s: 10.3.36, 10.4.26, 10.5.17, 10.6.9, 10.7.5, 10.8.4, 10.9.2, 10.10.1

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


 Description   

http://buildbot.askmonty.org/buildbot/builders/bld-starfs-release/builds/577/steps/test/logs/stdio

innodb.update_time 'innodb'              w2 [ fail ]
        Test ended at 2017-12-16 10:01:56
 
CURRENT_TEST: innodb.update_time
--- /opt/buildbot-slave/mariadb/starfsmenn2/build/mysql-test/suite/innodb/r/update_time.result	2017-12-14 18:23:31.087061690 -0500
+++ /opt/buildbot-slave/mariadb/starfsmenn2/build/mysql-test/suite/innodb/r/update_time.reject	2017-12-16 10:01:56.799233773 -0500
@@ -29,7 +29,7 @@
 SELECT COUNT(*) FROM information_schema.innodb_buffer_page
 WHERE table_name = '`test`.`t`';
 COUNT(*)
-0
+1
 SELECT COUNT(*) FROM information_schema.tables WHERE table_name = 't'
 AND update_time IS NOT NULL;
 COUNT(*)
 
mysqltest: Result content mismatch



 Comments   
Comment by Marko Mäkelä [ 2021-10-19 ]

The test contains an inherent race condition. If page flushing proceeds quicker than expected, then not all pages of the table might be evicted. This was rather easily repeatable in a 10.6-based branch that included the page flushing performance fix MDEV-26827.

I tried to make the failure less probable by halving the buffer pool to the minimal size (innodb_buffer_pool_size=5M).

Comment by Marko Mäkelä [ 2022-08-01 ]

According to monty, this test still fails.

On a closer look, I do not see the point of this test. The update_time is stored in the table metadata (dict_table_t); it has nothing to do with buffer pool page eviction or replacement. There is another test innodb.update_time_wl6658 that seems much more useful than this one.

Comment by Marko Mäkelä [ 2022-08-01 ]

I removed the buffer pool related test. I retained a test that covers XA COMMIT after server restart.

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