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

Test failure in main.partition_innodb

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 10.0.15
    • Fix Version/s: 10.0.16
    • Component/s: Tests
    • Labels:
      None

      Description

      http://buildbot.askmonty.org/buildbot/reports/cross_reference#branch=&revision=&platform=&dt=&bbnum=&typ=&info=&fail_name=main.partition_innodb&fail_variant=&fail_info_short=&fail_info_full=db.opt&limit=100

      CURRENT_TEST: main.partition_innodb --- /mnt/buildbot/build/mariadb-10.0.15/mysql-test/r/partition_innodb.result 2014-11-25 12:12:48.000000000 +0200 +++ /mnt/buildbot/build/mariadb-10.0.15/mysql-test/r/partition_innodb.reject 2014-11-26 02:28:43.000000000 +0200 @@ -541,6 +541,7 @@ PARTITION BY list(a) (PARTITION p1 VALUES IN (1)); CREATE INDEX i1 ON t1 (a); DROP TABLE t1; +db.opt # # Bug#54783: optimize table crashes with invalid timestamp default value and NO_ZERO_DATE # mysqltest: Result length mismatch

      Jan, looks like this was introduced with this commit of yours:

      revno: 4513
      revision-id: jplindst@mariadb.org-20141125093801-nrsv7259uxzlu4ub
      parent: jplindst@mariadb.org-20141125063103-r7q5vxxw0mfpc55p
      committer: Jan Lindström <jplindst@mariadb.org>
      branch nick: 10.0-bugs
      timestamp: Tue 2014-11-25 11:38:01 +0200
      message:
        MDEV-7046: MySQL#74480 - Failing assertion: os_file_status(newpath, &exists, &type) 
        after Operating system error number 36 in a file operation.

      Apparently the new testcase leaves stuff around that breaks following tests.

      You can see this, if you run the test like this:

      ./mtr --mem innodb.innodb-mdev7046 main.partition_innodb
       
      innodb.innodb-mdev7046 'innodb_plugin'   [ pass ]    141
      main.partition_innodb 'innodb_plugin'    [ fail ]
              Test ended at 2014-11-26 11:20:15
       
      CURRENT_TEST: main.partition_innodb
      --- /home/knielsen/my/10.0/work-10.0/mysql-test/r/partition_innodb.result	2014-10-16 15:19:35.500341000 +0200
      +++ /home/knielsen/my/10.0/work-10.0/mysql-test/r/partition_innodb.reject	2014-11-26 11:20:15.083007691 +0100
      @@ -541,6 +541,7 @@
       PARTITION BY list(a) (PARTITION p1 VALUES IN (1));
       CREATE INDEX i1 ON t1 (a);
       DROP TABLE t1;
      +db.opt
       #
       # Bug#54783: optimize table crashes with invalid timestamp default value and NO_ZERO_DATE
       #
       
      mysqltest: Result length mismatch

      The main.partition_innodb fails. But if you run it like this:

      ./mtr --mem main.partition_innodb)
       
      main.partition_innodb 'innodb_plugin'    [ pass ]   5918
      main.partition_innodb 'xtradb'           [ pass ]   6275

      it passes.

      So the test failures depends on the order in which tests are run. It only
      occurs if innodb.innodb-mdev7046 is run before main.partition_innodb (with no
      server restarts in-between).

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                jplindst Jan Lindström
                Reporter:
                knielsen Kristian Nielsen
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: