[MDEV-13888] innodb_fts.innodb_fts_plugin failed in buildbot with errors in server log Created: 2017-09-22  Updated: 2022-08-30  Resolved: 2022-08-30

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.2
Fix Version/s: 10.3.37, 10.4.27, 10.5.18, 10.6.10, 10.7.6, 10.8.5, 10.9.3, 10.10.2

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


 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-deb-zesty-amd64/builds/606/steps/mtr/logs/stdio

innodb_fts.innodb_fts_plugin 'innodb'    w2 [ fail ]  Found warnings/errors in server log file!
 
        Test ended at 2017-09-06 15:02:02
 
line
 
2017-09-06 15:01:58 139764074350784 [ERROR] mysqld: Table './mysql/plugin' is marked as crashed and should be repaired
 
2017-09-06 15:01:58 139764074350784 [ERROR] mysqld: Table 'plugin' is marked as crashed and should be repaired
 
2017-09-06 15:01:58 139764074350784 [Warning] Checking table:   './mysql/plugin'
 
2017-09-06 15:01:58 139764074350784 [ERROR] mysql.plugin: 1 client is using or hasn't closed the table properly
 
^ Found warnings in /dev/shm/var/2/log/mysqld.1.err



 Comments   
Comment by Marko Mäkelä [ 2022-08-30 ]

I suspect that the warnings occurred on slower builders where the server shutdown would time out and the server be forcibly killed. I added a FLUSH TABLES statement after the INSTALL PLUGIN statement to fix that.

Apart from this, the test occasionally delivered results in a different order. I fixed that by adding ORDER BY id to each SELECT statement that would return multiple rows.

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