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

Official Ubuntu 16.04 builds unsuccessful due to TokuDB test suite fails

    Details

      Description

      It was discovered, that MariaDB 10.0 builds done by official Ubuntu infrastructure on Launchpad randomly has failures in TokuDB tests:

      Failing test(s): tokudb.rows-32m-0 tokudb.rows-32m-1 tokudb.savepoint-5 tokudb_bugs.frm_store2 tokudb_bugs.frm_store3 plugins.show_all_plugins
      

      Example of one failure:

      tokudb.rows-32m-0                        w1 [ fail ]  timeout after 1800 seconds
              Test ended at 2016-03-05 22:12:06
       
      Test case timeout after 1800 seconds
       
      == /«PKGBUILDDIR»/builddir/mysql-test/var/1/log/rows-32m-0.log == 
      SET DEFAULT_STORAGE_ENGINE='tokudb';
      call mtr.add_suppression("TokuDB.*");
      call mtr.add_suppression(".*returned handler error 22");
      drop table if exists t;
      create table t (id int not null primary key, v longblob not null);
      select @@max_allowed_packet into @my_max_allowed_packet;
      set global max_allowed_packet=100000000;
      insert into t values (1,repeat('a',32*1024*1024));
      ERROR HY000: Got error 22 "Invalid argument" from storage engine TokuDB
      insert into t values (1,repeat('a',32*1024*1024-1));
      ERROR HY000: Got error 22 "Invalid argument" from storage engine TokuDB
      insert into t values (1,repeat('a',32*1024*1024-2));
      ERROR HY000: Got error 22 "Invalid argument" from storage engine TokuDB
      insert into t values (1,repeat('a',32*1024*1024-3));
      ERROR HY000: Got error 22 "Invalid argument" from storage engine TokuDB
      insert into t values (1,repeat('a',32*1024*1024-4));
      
      

      See recent log at https://launchpadlibrarian.net/252003566/buildlog_ubuntu-xenial-amd64.mariadb-10.0_10.0.24-5ubuntu2_BUILDING.txt.gz
      Overview of mariadb-10.0 builds on their way into the Ubuntu 16.04 repository: https://launchpad.net/ubuntu/+source/mariadb-10.0/+publishinghistory

      This test failure leads to the whole build exiting as unsuccessful, which in turn stops the new MariaDB package revision to enter the Ubuntu 16.04 archive.

      The issue is hard to reproduce. I've seen it a few times in our own MariaDB test PPA, e.g
      https://launchpadlibrarian.net/246287701/buildlog_ubuntu-xenial-amd64.mariadb-10.0_10.0.24-2~xenial1~1457210767.8871a3b_BUILDING.txt.gz
      https://launchpadlibrarian.net/245709429/buildlog_ubuntu-xenial-amd64.mariadb-10.0_10.0.24-2~xenial1~1457073991.8871a3b_BUILDING.txt.gz
      https://launchpadlibrarian.net/240974021/buildlog_ubuntu-xenial-amd64.mariadb-10.0_10.0.24-1~xenial1~1456004579.d20a814_BUILDING.txt.gz

      Overview: https://launchpad.net/~mysql-ubuntu/+archive/ubuntu/mariadb-10.0/+builds?build_text=&build_state=all

      I just triggered multiple builds in a row but they are all successful.

      I have not seen this issue surface on official Debian build systems.

      I managed though to reproduce this partially in my own build system in a xenial environment: http://labs.seravo.fi/~otto/debian/mariadb-10.0-xenial-amd64/mariadb-10.0_10.0.24-5_amd64.build-d7c9399-pbuilder.log Interestingly though the test suite does not exit properly despite failing TokuDB tests and the build ends up being successful.

      I have no idea how to proceed with this. Please somebody pick this up.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                cvicentiu Vicențiu Ciorbaru
                Reporter:
                otto Otto Kekäläinen
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: