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

TokuDB tests fail in buildbot with Assertion `global_status_var.global_memory_used == 0'

    XMLWordPrintable

Details

    Description

      http://buildbot.askmonty.org/buildbot/builders/kvm-bintar-centos6-amd64-debug/builds/864/steps/test/logs/stdio

      10.2 3473e0452ed5edb567f49b26c9f506431e175ac4

      tokudb_bugs.PS-3773                      w4 [ fail ]  Found warnings/errors in server log file!
              Test ended at 2018-09-15 07:25:53
      line
      mysqld: /home/buildbot/buildbot/build/sql/mysqld.cc:2176: void mysqld_exit(int): Assertion `global_status_var.global_memory_used == 0' failed.
      Attempting backtrace. You can use the following information to find out
      ^ Found warnings in /usr/local/mariadb-10.2.18-linux-x86_64/mysql-test/var/4/log/mysqld.1.err
      ok
       
       - found 'core.31336' (4/0)
       
      Trying 'dbx' to get a backtrace
      worker[4] > Restart  - not started
      gdb not found, cannot get the stack trace
      Compressed file /usr/local/mariadb-10.2.18-linux-x86_64/mysql-test/var/4/log/tokudb_bugs.PS-3773/mysqld.1/data/core.31336
       - found 'core.20404' (5/0)
       
      Trying 'dbx' to get a backtrace
      gdb not found, cannot get the stack trace
      Compressed file /usr/local/mariadb-10.2.18-linux-x86_64/mysql-test/var/4/log/tokudb_bugs.PS-3773/mysqld.1/data/core.20404
       - skipping '/usr/local/mariadb-10.2.18-linux-x86_64/mysql-test/var/4/log/tokudb_bugs.PS-3773/'
      

      Failing test(s): tokudb.compressions tokudb.dir_per_db_rename_to_nonexisting_schema tokudb_bugs.PS-3773 tokudb_bugs.frm_store tokudb_bugs.frm_store2 tokudb_bugs.frm_store3
      

      Attachments

        Activity

          People

            serg Sergei Golubchik
            elenst Elena Stepanova
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.