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

TokuDB crashes in build tests on Launchpad

    XMLWordPrintable

Details

    • 10.0.22, 10.1.9-1, 10.1.9-2, 10.1.9-3

    Description

      (Originally reported on mailing list, see thread at https://lists.launchpad.net/maria-developers/msg08111.html)

      I repeatedly get these test failures when running MariaDB builds on
      Launchpad: rpl-tokudb.tokudb_innodb_xa_crash tokudb_bugs.mdev4533
      tokudb.simple_join_tokudb_innodb tokudb.truncate_txn_rollback_innodb
      tokudb_bugs.5733_innodb

      The build run log can be viewed at
      https://launchpad.net/~mysql-ubuntu/+archive/ubuntu/mariadb-10.0/+builds?build_text=&build_state=all
      and it links to the individual build logs. All amd64 builds fail while
      all i386 (where TokuDB is disabled) pass OK. Sounds very much like a
      TokuDB-related issue. Or could the problem be something else and the
      TokuDB tests are just the first victim?

      Example of a recent log:
      https://launchpadlibrarian.net/196425361/buildlog_ubuntu-vivid-amd64.mariadb-10.0_10.0.16-1~exp3~vivid1~1422913379_FAILEDTOBUILD.txt.gz

      One example of the test outputs:

      rpl-tokudb.tokudb_innodb_xa_crash 'mix,xtradb' [ fail ]
              Test ended at 2015-02-02 22:29:06
       
      CURRENT_TEST: rpl-tokudb.tokudb_innodb_xa_crash
       
       
      Failed to start mysqld.1
      mysqltest failed but provided no output
       
       
       - saving '/build/buildd/mariadb-10.0-10.0.16/builddir/mysql-test/var/log/rpl-tokudb.tokudb_innodb_xa_crash-mix,xtradb/'
      to '/build/buildd/mariadb-10.0-10.0.16/builddir/mysql-test/var/log/rpl-tokudb.tokudb_innodb_xa_crash-mix,xtradb/'
       - found 'core' (1/5)
       
      Trying 'dbx' to get a backtrace
       
      Trying 'gdb' to get a backtrace
      Compressed file
      /build/buildd/mariadb-10.0-10.0.16/builddir/mysql-test/var/log/rpl-tokudb.tokudb_innodb_xa_crash-mix,xtradb/mysqld.1/data/core
      ***Warnings generated in error logs during shutdown after running
      tests: rpl-tokudb.tokudb_innodb_xa_crash
       
      150202 22:29:05 [ERROR] mysqld got signal 11 ;
      Attempting backtrace. You can use the following information to find out
      150202 22:29:05 [ERROR] mysqld got signal 11 ;
      Attempting backtrace. You can use the following information to find out

      Make options are visible in
      https://github.com/ottok/mariadb-10.0/blob/master/debian/rules

      Getting core dumps from Launchpad is not possible, nobody has file system access to builds. Only output channel is build logs.

      The old issue might be related: https://mariadb.atlassian.net/browse/MDEV-5618 and https://tokutek.atlassian.net/browse/DB-509

      Attachments

        Issue Links

          Activity

            People

              bar Alexander Barkov
              otto Otto Kekäläinen
              Votes:
              0 Vote for this issue
              Watchers:
              4 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.