Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-7870

parts.partition_alter4_innodb fails sporadically in buildbot with "Protocol::end_statement(): Assertion `0' failed"

    Details

      Description

      http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2/builds/3583/steps/test_3/logs/stdio

      parts.partition_alter4_innodb 'xtradb'   w2 [ fail ]
              Test ended at 2015-03-26 03:42:59
       
      CURRENT_TEST: parts.partition_alter4_innodb
      mysqltest: In included file "./suite/parts/inc/partition_trigg1.inc": 
      included from ./suite/parts/inc/partition_check.inc at line 978:
      included from ./suite/parts/inc/partition_alter_1.inc at line 71:
      included from ./suite/parts/inc/partition_alter_41.inc at line 59:
      included from ./suite/parts/inc/partition_alter4.inc at line 63:
      included from /mnt/buildbot/build/mariadb-10.0.17/mysql-test/suite/parts/t/partition_alter4_innodb.test at line 80:
      At line 38: query 'CREATE TRIGGER trg_1 $event ON $tab_has_trigg FOR EACH ROW
      BEGIN
      UPDATE $tab_in_trigg SET f_int1 = -f_int1, f_int2 = -f_int2,
      f_charbig = 'updated by trigger'
            WHERE f_int1 = new.f_int1;
      END' failed: 2013: Lost connection to MySQL server during query
       
      The result from queries just before the failure was:
      < snip >
      UPDATE t1 SET f_charbig = REPEAT('b', 1000);
      	
      # check special-1 success: 	1
      UPDATE t1 SET f_charbig = '';
      	
      # check special-2 success: 	1
      UPDATE t1 SET f_charbig = CONCAT('===',CAST(f_int1 AS CHAR),'===');
      INSERT INTO t1(f_int1,f_int2,f_char1,f_char2,f_charbig)
      SELECT f_int1,f_int2,f_char1,f_char2,'just inserted' FROM t0_template
      WHERE f_int1 BETWEEN @max_row_div2 - 1 AND @max_row_div2 + 1;
      INSERT INTO t0_aux(f_int1,f_int2,f_char1,f_char2,f_charbig)
      SELECT -f_int1,-f_int1,CAST(-f_int1 AS CHAR),CAST(-f_int1 AS CHAR),
      'just inserted' FROM t0_template
      WHERE f_int1 BETWEEN @max_row_div2 - 1 AND @max_row_div2 + 1;
      CREATE TRIGGER trg_1 BEFORE INSERT ON t0_aux FOR EACH ROW
      BEGIN
      UPDATE t1 SET f_int1 = -f_int1, f_int2 = -f_int2,
      f_charbig = 'updated by trigger'
            WHERE f_int1 = new.f_int1;
      END|
       
      More results from queries before failure can be found in /mnt/buildbot/build/mariadb-10.0.17/mysql-test/var/2/log/partition_alter4_innodb.log
       
       
      Server [mysqld.1 - pid: 19096, winpid: 19096, exit: 256] failed during test run
      Server log from this test:
      ----------SERVER LOG START-----------
      mysqld: /home/buildbot/buildbot/build/mariadb-10.0.17/sql/protocol.cc:522: void Protocol::end_statement(): Assertion `0' failed.
      150326  3:42:38 [ERROR] mysqld got signal 6 ;
      This could be because you hit a bug. It is also possible that this binary
      or one of the libraries it was linked against is corrupt, improperly built,
      or misconfigured. This error can also be caused by malfunctioning hardware.
       
      To report this bug, see http://kb.askmonty.org/en/reporting-bugs
       
      We will try our best to scrape up some info that will hopefully help
      diagnose the problem, but since we have already crashed, 
      something is definitely wrong and this may fail.
       
      Server version: 10.0.17-MariaDB-debug-log
      key_buffer_size=1048576
      read_buffer_size=131072
      max_used_connections=2
      max_threads=153
      thread_count=1
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 61867 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x0xb461ee8
      Attempting backtrace. You can use the following information to find out
      where mysqld died. If you see no messages after this, something went
      terribly wrong...
      stack_bottom = 0xababb29c thread_stack 0x48000
      mysys/stacktrace.c:246(my_print_stacktrace)[0x8aa5d49]
      sql/signal_handler.cc:153(handle_fatal_signal)[0x83dd8a4]
      [0xb76e4400]
      [0xb76e4424]
      /lib/i386-linux-gnu/libc.so.6(gsignal+0x4f)[0xb73c11ef]
      /lib/i386-linux-gnu/libc.so.6(abort+0x175)[0xb73c4835]
      /lib/i386-linux-gnu/libc.so.6(+0x27095)[0xb73ba095]
      /lib/i386-linux-gnu/libc.so.6(+0x27147)[0xb73ba147]
      sql/protocol.cc:522(Protocol::end_statement())[0x8190693]
      sql/sql_parse.cc:1722(dispatch_command(enum_server_command, THD*, char*, unsigned int))[0x8239d65]
      sql/sql_parse.cc:996(do_command(THD*))[0x823c5cc]
      sql/sql_connect.cc:1375(do_handle_one_connection(THD*))[0x83298e0]
      sql/sql_connect.cc:1291(handle_one_connection)[0x83299cf]
      perfschema/pfs.cc:1863(pfs_spawn_thread)[0x85b39aa]
      /lib/i386-linux-gnu/libpthread.so.0(+0x6d4c)[0xb766ed4c]
      /lib/i386-linux-gnu/libc.so.6(clone+0x5e)[0xb747dace]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0xae5049f0): CREATE TRIGGER trg_1 BEFORE INSERT ON t0_aux FOR EACH ROW BEGIN UPDATE t1 SET f_int1 = -f_int1, f_int2 = -f_int2, f_charbig = 'updated by trigger'       WHERE f_int1 = new.f_int1; END
      Connection ID (thread ID): 35
      Status: NOT_KILLED
       
      Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on
       
      The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
      information that should help you find out what is causing the crash.
      Writing a core file
      ----------SERVER LOG END-------------
       
       
       - saving '/mnt/buildbot/build/mariadb-10.0.17/mysql-test/var/2/log/parts.partition_alter4_innodb-xtradb/' to '/mnt/buildbot/build/mariadb-10.0.17/mysql-test/var/log/parts.partition_alter4_innodb-xtradb/'

      Retry passed.

      So far it happened 3 times according to the buildbot database (on some reason cross-reference report fails to fetch these failures, gives an error on loading data).
      Twice it was with InnoDB plugin, and once with XtraDB; always on the same line of the test.

      I tried to reproduce it on work, with the same sources, same build options and same test sequence, but couldn't.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                elenst Elena Stepanova
                Reporter:
                elenst Elena Stepanova
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: