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

MTR's internal check of the test case 'tokudb.dir_per_db_rename_to_nonexisting_schema' failed

    XMLWordPrintable

Details

    Description

      The person from Debian who was about to upload to Debian 8 (jessie) a 10.0.36-1 release prepared by me got the following test suite failure during the standard build:

      tokudb.dir_per_db_rename_to_nonexisting_schema [ pass ]   3793
       
      MTR's internal check of the test case 'tokudb.dir_per_db_rename_to_nonexisting_schema' failed.
      This means that the test case does not preserve the state that existed
      before the test case was executed.  Most likely the test case did not
      do a proper clean-up. It could also be caused by the previous test run
      by this thread, if the server wasn't restarted.
      This is the diff of the states of the servers before and after the
      test case was executed:
      mysqltest: Logging to '/build/mariadb-10.0-10.0.36/builddir/mysql-test/var/tmp/check-mysqld_1.log'.
      mysqltest: Results saved in '/build/mariadb-10.0-10.0.36/builddir/mysql-test/var/tmp/check-mysqld_1.result'.
      mysqltest: Connecting to server localhost:16000 (socket /build/mariadb-10.0-10.0.36/builddir/mysql-test/var/tmp/mysqld.1.sock) as 'root', connection 'default', attempt 0 ...
      mysqltest: ... Connected.
      mysqltest: Start processing test commands from './include/check-testcase.test' ...
      mysqltest: ... Done processing test commands.
      --- /build/mariadb-10.0-10.0.36/builddir/mysql-test/var/tmp/check-mysqld_1.result	2018-08-29 17:41:16.511000000 +0000
      +++ /build/mariadb-10.0-10.0.36/builddir/mysql-test/var/tmp/check-mysqld_1.reject	2018-08-29 17:41:20.758000000 +0000
      @@ -385,7 +385,7 @@
       TOKUDB_BLOCK_SIZE	4194304
       TOKUDB_BULK_FETCH	ON
       TOKUDB_CACHETABLE_POOL_THREADS	0
      -TOKUDB_CACHE_SIZE	1193013248
      +TOKUDB_CACHE_SIZE	1436006400
       TOKUDB_CARDINALITY_SCALE_PERCENT	50
       TOKUDB_CHECKPOINTING_PERIOD	60
       TOKUDB_CHECKPOINT_LOCK	OFF
      @@ -418,7 +418,7 @@
       TOKUDB_LOCK_TIMEOUT	4000
       TOKUDB_LOCK_TIMEOUT_DEBUG	1
       TOKUDB_LOG_DIR	
      -TOKUDB_MAX_LOCK_MEMORY	149126656
      +TOKUDB_MAX_LOCK_MEMORY	179500800
       TOKUDB_OPTIMIZE_INDEX_FRACTION	1.000000
       TOKUDB_OPTIMIZE_INDEX_NAME	
       TOKUDB_OPTIMIZE_THROTTLE	0
       
      mysqltest: Result content mismatch
       
      not ok
      

      tokudb_alter_table.di_dui                [ pass ]    971
      tokudb_alter_table.drop_add_pk_104       [ pass ]    449
      tokudb_alter_table.drop_pk_with_prefix   [ pass ]   2473
      tokudb_alter_table.frm_discover          [ pass ]   1191
      tokudb_alter_table.hcad_all_add          [ pass ]  773630
      Test suite timeout! Terminating...
       
      Only  4370  of 5901 completed.
      --------------------------------------------------------------------------
      The servers were restarted 1026 times
      Spent 26910.649 of 32433 seconds executing testcases
       
      Check of testcase failed for: tokudb.dir_per_db_rename_to_nonexisting_schema
       
      Timeout: All 3580 tests were successful.
       
      633 tests were skipped, 211 by the test itself.
      

      So the build fails with an unusual timeout, and one test that passed still yields the error above.

      A recent identically prepared upload to Ubuntu Xenial built and passes the test suite just fine:
      https://launchpad.net/ubuntu/+source/mariadb-10.0/10.0.36-0ubuntu0.16.04.1

      The exact same commit uploaded to a Ubuntu based builder did not have this 'tokudb.dir_per_db_rename_to_nonexisting_schema' failure.

      Attachments

        Activity

          People

            Unassigned Unassigned
            otto Otto Kekäläinen
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.