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

Multiple test failures on mips and mipsel platforms, suites federated and rpl

    XMLWordPrintable

Details

    • 10.0.22, 10.1.9-1, 10.1.9-2

    Description

      On Debian build system, architectures mips and mipsel fail to build properly due to multiple failing tests.

      Failing test(s): federated.federated_partition federated.federated_transactions federated.federated_innodb multi_source.gtid multi_source.multisource rpl.rpl_auto_increment rpl.rpl_invoked_features rpl.rpl_partition_innodb

      See full logs at

      Builds overview (latest package at the moment is 10.0.21-2 in Debian experimental):

      Examples of failures:

      worker[1] mysql-test-run: WARNING: Process [mysqld.1 - pid: 22599, winpid: 22599, exit: 256] died after mysql-test-run waited 3.1 seconds for /«PKGBUILDDIR»/builddir/mysql-test/var/run/mysqld.1.pid to be created.
      federated.federated_partition 'X,innodb_plugin' [ fail ]
              Test ended at 2015-08-28 03:51:35
       
      CURRENT_TEST: federated.federated_partition
       
       
      Failed to start mysqld.1
      mysqltest failed but provided no output
       
       
       - saving '/«PKGBUILDDIR»/builddir/mysql-test/var/log/federated.federated_partition-X,innodb_plugin/' to '/«PKGBUILDDIR»/builddir/mysql-test/var/log/federated.federated_partition-X,innodb_plugin/'
       - found 'core' (0/5)
       
      Trying 'dbx' to get a backtrace
       
      Trying 'gdb' to get a backtrace
      Compressed file /«PKGBUILDDIR»/builddir/mysql-test/var/log/federated.federated_partition-X,innodb_plugin/mysqld.2/data/core
       - found 'core' (1/5)
       
      Trying 'dbx' to get a backtrace
       
      Trying 'gdb' to get a backtrace
      Compressed file /«PKGBUILDDIR»/builddir/mysql-test/var/log/federated.federated_partition-X,innodb_plugin/mysqld.1/data/core
      ***Warnings generated in error logs during shutdown after running tests: federated.federated_partition
       
      150828  3:51:31 [ERROR] mysqld got signal 11 ;
      Attempting backtrace. You can use the following information to find out
      150828  3:51:31 [ERROR] mysqld got signal 11 ;
      Attempting backtrace. You can use the following information to find out
       
      worker[1] mysql-test-run: WARNING: Process [mysqld.1 - pid: 22647, winpid: 22647, exit: 256] died after mysql-test-run waited 2.3 seconds for /«PKGBUILDDIR»/builddir/mysql-test/var/run/mysqld.1.pid to be created.
      federated.federated_transactions 'X,innodb_plugin' [ fail ]
              Test ended at 2015-08-28 03:52:06
       
      CURRENT_TEST: federated.federated_partition
      CURRENT_TEST: federated.federated_transactions
       
       
      Failed to start mysqld.1
       
       
       - saving '/«PKGBUILDDIR»/builddir/mysql-test/var/log/federated.federated_transactions-X,innodb_plugin/' to '/«PKGBUILDDIR»/builddir/mysql-test/var/log/federated.federated_transactions-X,innodb_plugin/'
       - found 'core' (2/5)
       
      Trying 'dbx' to get a backtrace
       
      Trying 'gdb' to get a backtrace
      worker[1] mysql-test-run: WARNING: Process [mysqld.1 - pid: 22677, winpid: 22677, exit: 256] died after mysql-test-run waited 3.8 seconds for /«PKGBUILDDIR»/builddir/mysql-test/var/run/mysqld.1.pid to be created.
      Compressed file /«PKGBUILDDIR»/builddir/mysql-test/var/log/federated.federated_transactions-X,innodb_plugin/mysqld.2/data/core
       - found 'core' (3/5)
       
      Trying 'dbx' to get a backtrace
       
      Trying 'gdb' to get a backtrace
      Compressed file /«PKGBUILDDIR»/builddir/mysql-test/var/log/federated.federated_transactions-X,innodb_plugin/mysqld.1/data/core
      ***Warnings generated in error logs during shutdown after running tests: federated.federated_transactions
       
      150828  3:52:04 [ERROR] mysqld got signal 11 ;
      Attempting backtrace. You can use the following information to find out
      150828  3:52:04 [ERROR] mysqld got signal 11 ;
      Attempting backtrace. You can use the following information to find out
       
      federated.federated_innodb 'X,innodb_plugin' [ fail ]
              Test ended at 2015-08-28 03:52:36
       
      CURRENT_TEST: federated.federated_partition
      CURRENT_TEST: federated.federated_transactions
      CURRENT_TEST: federated.federated_innodb
       
       
      Failed to start mysqld.1
       
       
       - saving '/«PKGBUILDDIR»/builddir/mysql-test/var/log/federated.federated_innodb-X,innodb_plugin/' to '/«PKGBUILDDIR»/builddir/mysql-test/var/log/federated.federated_innodb-X,innodb_plugin/'
       - found 'core' (4/5)
       
      Trying 'dbx' to get a backtrace
       
      Trying 'gdb' to get a backtrace
      Compressed file /«PKGBUILDDIR»/builddir/mysql-test/var/log/federated.federated_innodb-X,innodb_plugin/mysqld.2/data/core
       - found 'core' (5/5)
       
      Trying 'dbx' to get a backtrace
       
      Trying 'gdb' to get a backtrace
       - deleting it, already saved 5
      ***Warnings generated in error logs during shutdown after running tests: federated.federated_innodb
       
      150828  3:52:08 [ERROR] mysqld got signal 11 ;
      Attempting backtrace. You can use the following information to find out
      150828  3:52:08 [ERROR] mysqld got signal 11 ;
      Attempting backtrace. You can use the following information to find out
       
      worker[1] mysql-test-run: WARNING: Process [mysqld.1 - pid: 25115, winpid: 25115, exit: 256] died after mysql-test-run waited 2.5 seconds for /«PKGBUILDDIR»/builddir/mysql-test/var/run/mysqld.1.pid to be created.
      rpl.rpl_auto_increment 'innodb_plugin,row' [ fail ]
              Test ended at 2015-08-28 03:54:38
       
      CURRENT_TEST: rpl.rpl_auto_increment
       
       
      Failed to start mysqld.1
      mysqltest failed but provided no output
      The result from queries just before the failure was:
      < snip >
      DROP TABLE t_ignored1;
      DROP TABLE t_ignored2;
      CREATE TABLE t1 (id SMALLINT UNSIGNED NOT NULL AUTO_INCREMENT PRIMARY KEY, data INT) ENGINE=innodb;
      BEGIN;
      # Set sql_mode with NO_AUTO_VALUE_ON_ZERO for allowing
      # zero to fill the auto_increment field.
      SET SQL_MODE=NO_AUTO_VALUE_ON_ZERO;
      INSERT INTO t1(id,data) VALUES(0,2);
      # Resetting sql_mode without NO_AUTO_VALUE_ON_ZERO to
      # affect the execution of the transaction on slave.
      SET SQL_MODE=0;
      COMMIT;
      SELECT * FROM t1;
      id	data
      0	2
      SELECT * FROM t1;
      id	data
      0	2
      DROP TABLE t1;
      include/rpl_end.inc
       
       
       
       - saving '/«PKGBUILDDIR»/builddir/mysql-test/var/log/rpl.rpl_auto_increment-innodb_plugin,row/' to '/«PKGBUILDDIR»/builddir/mysql-test/var/log/rpl.rpl_auto_increment-innodb_plugin,row/'
       - found 'core' (15/5)
       
      Trying 'dbx' to get a backtrace
       
      Trying 'gdb' to get a backtrace
       - deleting it, already saved 5
       - found 'core' (16/5)
       
      Trying 'dbx' to get a backtrace
       
      Trying 'gdb' to get a backtrace
       - deleting it, already saved 5
      ***Warnings generated in error logs during shutdown after running tests: rpl.rpl_auto_increment
       
      150828  3:54:36 [ERROR] mysqld got signal 11 ;
      Attempting backtrace. You can use the following information to find out
      150828  3:54:36 [ERROR] mysqld got signal 11 ;
      Attempting backtrace. You can use the following information to find out
       
      rpl.rpl_auto_increment 'row,xtradb'      [ pass ]   2712

      Notes:

      • mips and mipsel logs seem identical
      • all test failures occur because mysqld crashes
      • 37 tests did succeed so the mips(el) build is not completely broken
      • this is not an regression, even 10.0.14 build logs for mips show same failures

      Attachments

        Issue Links

          Activity

            People

              cvicentiu Vicențiu Ciorbaru
              otto Otto Kekäläinen
              Votes:
              0 Vote for this issue
              Watchers:
              6 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.