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

main.range_vs_index_merge_innodb fails in buildbot with timeout

    Details

    • Sprint:
      10.1.32

      Description

      http://buildbot.askmonty.org/buildbot/builders/work-amd64-valgrind/builds/10024/steps/test/logs/stdio

      main.range_vs_index_merge_innodb 'xtradb' w4 [ fail ]  timeout after 9000 seconds
              Test ended at 2017-04-28 01:02:38
       
      Test case timeout after 9000 seconds
       
      == /mnt/data/buildot/maria-slave/work-opensuse-amd64/build/mysql-test/var/4/log/range_vs_index_merge_innodb.log == 
      create table t1 (
      id int unsigned auto_increment primary key,
      c1 char(12),
      c2 char(15),
      c3 char(1)
      );
      insert into t1 (c3) values ('1'), ('2');
      insert into t1 (c3) select c3 from t1;
      insert into t1 (c3) select c3 from t1;
      insert into t1 (c3) select c3 from t1;
      insert into t1 (c3) select c3 from t1;
      insert into t1 (c3) select c3 from t1;
      insert into t1 (c3) select c3 from t1;
      insert into t1 (c3) select c3 from t1;
      insert into t1 (c3) select c3 from t1;
      insert into t1 (c3) select c3 from t1;
      insert into t1 (c3) select c3 from t1;
      insert into t1 (c3) select c3 from t1;
      insert into t1 (c3) select c3 from t1;
      update t1 set c1=lpad(id+1000, 12, ' '), c2=lpad(id+10000, 15, ' ');
       
      The server [mysqld.1 - pid: 5073, winpid: 5073, exit: 256] crashed while running 'analyze-timeout'
      Server log from this test:
      ----------SERVER LOG START-----------
      2017-04-27 22:32:00 68532992 [Note] InnoDB: Created tablespace for space 416 name world/Country key_id 0 encryption 0.
      2017-04-27 22:32:00 68532992 [Note] InnoDB: Created tablespace for space 417 name world/City key_id 0 encryption 0.
      2017-04-27 22:32:01 68532992 [Note] InnoDB: Created tablespace for space 418 name world/CountryLanguage key_id 0 encryption 0.
      2017-04-27 22:53:02 68532992 [Note] InnoDB: Created tablespace for space 419 name test/t1 key_id 0 encryption 0.
      2017-04-28  0:14:41 68532992 [Note] InnoDB: Created tablespace for space 420 name test/t1 key_id 0 encryption 0.
      2017-04-28  0:33:10 68532992 [Note] InnoDB: Created tablespace for space 421 name test/t1 key_id 0 encryption 0.
      2017-04-28  0:46:39 68532992 [Note] InnoDB: Created tablespace for space 422 name test/t1 key_id 0 encryption 0.
      170428  1:01:57 [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 https://mariadb.com/kb/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.1.23-MariaDB-debug
      key_buffer_size=1048576
      read_buffer_size=131072
      max_used_connections=1
      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 = 63027 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x0
      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 = 0x0 thread_stack 0x48400
      /mnt/data/buildot/maria-slave/work-opensuse-amd64/build/sql/mysqld(my_print_stacktrace+0x38)[0xf20d95]
      mysys/stacktrace.c:267(my_print_stacktrace)[0x868233]
      /lib64/libpthread.so.0(+0xf9f0)[0x4e439f0]
      /lib64/libc.so.6(__poll+0x2d)[0x6b2006d]
      sql/mysqld.cc:6484(handle_connections_sockets())[0x552e78]
      sql/mysqld.cc:5914(mysqld_main(int, char**))[0x551e44]
      sql/main.cc:26(main)[0x546d58]
      /lib64/libc.so.6(__libc_start_main+0xf5)[0x6a63be5]
      x86_64/start.S:125(_start)[0x546c49]
      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-------------
      

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                marko Marko Mäkelä
                Reporter:
                elenst Elena Stepanova
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: