[MDEV-10611] main.query_cache, rpl.rpl_switch_stm_row_mixed failed in buildbot Created: 2016-08-20  Updated: 2016-10-25  Resolved: 2016-10-25

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.0
Fix Version/s: 10.0.24

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Sergey Vojtovich
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-7069 Fix buildbot failures in main server ... Stalled
Sprint: 10.0.28

 Description   

http://buildbot.askmonty.org/buildbot/builders/bld-dan-debug/builds/3183/steps/test_1/logs/stdio

main.query_cache                         w2 [ fail ]  Found warnings/errors in server log file!
 
        Test ended at 2016-04-26 20:26:52
 
line
 
safe_mutex: Found wrong usage of mutex 'LOCK_thd_data' and 'LOCK_thread_count'
 
^ Found warnings in /opt/buildbot-slave/mariadb/dan_demeter1/build/mysql-test/var/2/log/mysqld.1.err
 
ok
 
 
 
 - saving '/opt/buildbot-slave/mariadb/dan_demeter1/build/mysql-test/var/2/log/main.query_cache/' to '/opt/buildbot-slave/mariadb/dan_demeter1/build/mysql-test/var/log/main.query_cache/'
 
 
 
Retrying test main.query_cache, attempt(2/3)...


10.0	44554d611194e2ac02e5beaf4b88ffe5	work-amd64-valgrind	2016-04-26 15:40:50	8708	nm	Valgrind run, no --ps-protocol	rpl.rpl_switch_stm_row_mixed	mix	Found warnings/errors in server log file!
 
rpl.rpl_switch_stm_row_mixed 'mix'       w5 [ fail ]  Found warnings/errors in server log file!
 
        Test ended at 2016-04-26 16:08:49
 
line
 
safe_mutex: Found wrong usage of mutex 'LOCK_thd_data' and 'LOCK_log'
 
safe_mutex: Found wrong usage of mutex 'LOCK_thd_data' and 'LOCK_thread_count'
 
^ Found warnings in /mnt/data/buildot/maria-slave/work-opensuse-amd64/build/mysql-test/var/5/log/mysqld.1.err
 
ok
 
 
 
 - saving '/mnt/data/buildot/maria-slave/work-opensuse-amd64/build/mysql-test/var/5/log/rpl.rpl_switch_stm_row_mixed-mix/' to '/mnt/data/buildot/maria-slave/work-opensuse-amd64/build/mysql-test/var/log/rpl.rpl_switch_stm_row_mixed-mix/'



 Comments   
Comment by Sergey Vojtovich [ 2016-10-25 ]

Likely introduced by https://github.com/MariaDB/server/commit/0dbc66498d9222d91b73d4c0a8a40c96bd3dc296
And fixed by https://github.com/MariaDB/server/commit/b7ad1ba5d121d4fe4b0655e46076b6e50754b4e9

According to bb logs it seem to happen only on 2016-04-26, which supports my guess. And I tend to remember we discussed with Monty this failure on that day.

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