• Chad MILLER's avatar
    Bug#21579 - innodb_concurrent random failures with varying differences · 2dcc449f
    Chad MILLER authored
    Due to unknown changes the test failed in some ways.
    
    Fixed by checking the test case in detail, commenting the expected behavior,
    and fixing error directives.
    
    In the course of the analyze unneeded get_lock()/release_lock() use,
    unneeded send/reap use, and unneeded sleeps were removed. The lock wait
    timeout was reduced to 1 second, so that this is no big-test any more.
    
    The test was split into two parts, one running the tests with
    --innodb_locks_unsafe_for_binlog, the other part without.
    The main part (include/concurrent.inc) conditionally expects
    lock wait timeouts based on the value of the system variable
    innodb_locks_unsafe_for_binlog.
    
    The major part of the patch comes from Kristofer Pettersson.
    
    (Chad queues this patch on demand by Trudy/Davi.)
    2dcc449f
concurrent_innodb_unsafelog.test 718 Bytes