5.5.13-eb multiple valgrind warnings

Bug #783885 reported by Valentine Gostev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
percona-projects-qa
Fix Released
High
Valentine Gostev

Bug Description

As agreed I am reporting here total list of valgrin warnings discovered. So later they could be forked into separate reports if necessary.

Failing tests with valgrind: (excluding failures from upstream)

rpl.rpl_semi_sync_event
rpl.rpl_semi_sync
rpl.rpl_err_ignoredtable
rpl.rpl_deadlock_innodb
rpl.rpl_stop_slave rpl.rpl_events
rpl.rpl_insert_id
rpl.rpl_slow_query_log
rpl.rpl_insert
rpl.rpl_stm_auto_increment_bug33029
rpl.rpl_stm_insert_delayed
rpl.rpl_concurrency_error
rpl.rpl_stm_start_stop_slave
rpl.rpl_circular_for_4_hosts
rpl.rpl_heartbeat_basic
sys_vars.all_vars
binlog.binlog_stm_mix_innodb_myisam
binlog.binlog_row_mix_innodb_myisam
binlog.binlog_stm_row
sys_vars.tx_isolation_func
binlog.binlog_killed
innodb.innodb
main.events_bugs
main.events_restart
innodb.innodb_mysql
main.partition_innodb_semi_consistent
main.log_tables
main.status
main.check
main.debug_sync
main.delayed
main.events_1
main.events_scheduling
main.handler_myisam
main.insert_notembedded
main.kill
main.lock_multi
main.myisam_debug
main.mysqld--help-notwin
main.mysqlslap
main.query_cache_notembedded
main.sp-threads
main.sp_notembedded
main.view
sys_vars.concurrent_insert_func
sys_vars.delayed_insert_limit_func
sys_vars.slow_launch_time_func
sys_vars.sql_low_priority_updates_func
sys_vars.thread_cache_size_func
sys_vars.wait_timeout_func
perfschema.func_file_io
perfschema.func_mutex
perfschema.global_read_lock
perfschema.myisam_file_io
perfschema.thread_cache
main.mdl_sync
main.lock_sync
main.concurrent_innodb_unsafelog
main.unsafe_binlog_innodb
innodb.innodb_mysql_rbk
main.concurrent_innodb_safelog
innodb.innodb_lock_wait_timeout_1
innodb.innodb_timeout_rollback
innodb.innodb-semi-consistent
main.innodb_mysql_lock
main.deadlock_innodb
main.flush_block_commit
main.handler_innodb
main.partition_innodb_plugin
main.xa innodb.innodb-timeout
innodb.innodb_bug42419
innodb.innodb_bug49164
innodb.innodb_bug51920
innodb.innodb_bug52663
innodb.innodb_information_schema
innodb.innodb_trx_weight
main.bug39022
main.innodb_mysql_lock2
perfschema.relaylog

Changed in percona-projects-qa:
milestone: none → 5.5.13-eb
assignee: nobody → Laurynas Biveinis (laurynas-biveinis)
Revision history for this message
Valentine Gostev (longbow) wrote :

Output of mtr

Changed in percona-projects-qa:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

I have pushed the fix that should fix a very big part (but not all) of failures. Can you re-run the testsuite? Hopefully the remaining failures will be easy to group now.

Changed in percona-projects-qa:
status: Triaged → In Progress
assignee: Laurynas Biveinis (laurynas-biveinis) → Valentine Gostev (core-longbow)
Revision history for this message
Valentine Gostev (longbow) wrote :

Laurynas,
few of them left

main.heap_bug783366
main.kill
main.sp-threads
sys_vars.thread_cache_size_func
perfschema.func_file_io
perfschema.func_mutex
perfschema.global_read_lock
perfschema.myisam_file_io
perfschema.thread_cache
perfschema.relaylog

Changed in percona-projects-qa:
assignee: Valentine Gostev (core-longbow) → Laurynas Biveinis (laurynas-biveinis)
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

How do I reproduce Valgrind errors with these? I tried ./mysql-test-run.pl --mem --mysqld=--thread_handling=pool-of-threads --valgrind <test-name>, and they all come valgrind-clean.

In any case, these test failures have their own bugs, so if there are any valgrind failures, let's add them to those bugs.

If heap_bug783366 fails for you, please reopen that bug.
The rest are already tracked, in the order of tests: #782106 #780473 #780502 #780722 #781035 #781065 #781069 #781075 #781092

Changed in percona-projects-qa:
assignee: Laurynas Biveinis (laurynas-biveinis) → Valentine Gostev (core-longbow)
status: In Progress → Fix Committed
Changed in percona-projects-qa:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.