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

innodb_zip.cmp_per_index failed in buildbot, result length mismatch

Details

    Description

      http://buildbot.askmonty.org/buildbot/builders/kvm-bintar-quantal-amd64/builds/8051/steps/test/logs/stdio

      CURRENT_TEST: innodb_zip.cmp_per_index
      		 
      --- /usr/local/mariadb-10.3.3-linux-x86_64/mysql-test/suite/innodb_zip/r/cmp_per_index.result	2017-11-10 16:20:59.000000000 +0200
      		 
      +++ /usr/local/mariadb-10.3.3-linux-x86_64/mysql-test/suite/innodb_zip/r/cmp_per_index.reject	2017-11-10 20:37:10.445862447 +0200
      		 
      @@ -91,11 +91,5 @@
      		 
       compress_ops	0
      		 
       compress_ops_ok	0
      		 
       uncompress_ops	6
      		 
      -database_name	test
      		 
      -table_name	t
      		 
      -index_name	PRIMARY
      		 
      -compress_ops	0
      		 
      -compress_ops_ok	0
      		 
      -uncompress_ops	5
      		 
       DROP TABLE t;
      		 
       SET GLOBAL innodb_cmp_per_index_enabled=default;
      		 
       
      		 
      mysqltest: Result length mismatch

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          alice Alice Sherepa created issue -
          marko Marko Mäkelä made changes -
          Field Original Value New Value
          Component/s Storage Engine - InnoDB [ 10129 ]
          marko Marko Mäkelä added a comment -

          I do not think that this failure is specific to 10.3. The ROW_FORMAT=COMPRESSED code has been mostly unchanged since 5.5.

          marko Marko Mäkelä added a comment - I do not think that this failure is specific to 10.3. The ROW_FORMAT=COMPRESSED code has been mostly unchanged since 5.5.
          marko Marko Mäkelä made changes -
          Assignee Thirunarayanan B [ thiru ]
          thiru Thirunarayanan Balathandayuthapani made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          thiru Thirunarayanan Balathandayuthapani added a comment -

          If the select query chooses the index 'b' then there is possibility for the issue to happen. It doesn't need
          to access the clustered index. Right now, select query does that only. When we open the table, it eventually
          opens the clustered index to update the stats. That;s why there is value for primary index.

          I think we can adjust the test case to make fetch from primary index always.

          thiru Thirunarayanan Balathandayuthapani added a comment - If the select query chooses the index 'b' then there is possibility for the issue to happen. It doesn't need to access the clustered index. Right now, select query does that only. When we open the table, it eventually opens the clustered index to update the stats. That;s why there is value for primary index. I think we can adjust the test case to make fetch from primary index always.
          marko Marko Mäkelä added a comment -

          Good analysis. FORCE INDEX should cure it. I think it should be done in MariaDB 5.5 already. If the test is missing or under a different name in MariaDB before 10.2, then the test should be added or renamed.

          marko Marko Mäkelä added a comment - Good analysis. FORCE INDEX should cure it. I think it should be done in MariaDB 5.5 already. If the test is missing or under a different name in MariaDB before 10.2, then the test should be added or renamed.
          thiru Thirunarayanan Balathandayuthapani made changes -
          Assignee Thirunarayanan B [ thiru ] Marko Mäkelä [ marko ]
          Status In Progress [ 3 ] In Review [ 10002 ]
          marko Marko Mäkelä added a comment -

          This looks OK to me, but please do it in the earliest applicable version instead of 10.3.
          The test exists in 10.2 already. It is missing from 10.0 and 10.1.
          I think that it suffices to modify the test in 10.2.

          marko Marko Mäkelä added a comment - This looks OK to me, but please do it in the earliest applicable version instead of 10.3. The test exists in 10.2 already. It is missing from 10.0 and 10.1. I think that it suffices to modify the test in 10.2.
          marko Marko Mäkelä made changes -
          Assignee Marko Mäkelä [ marko ] Thirunarayanan B [ thiru ]
          Status In Review [ 10002 ] Stalled [ 10000 ]
          thiru Thirunarayanan Balathandayuthapani made changes -
          Fix Version/s 10.2.15 [ 23006 ]
          Fix Version/s 10.3.7 [ 23005 ]
          Fix Version/s 10.3 [ 22126 ]
          Resolution Fixed [ 1 ]
          Status Stalled [ 10000 ] Closed [ 6 ]
          serg Sergei Golubchik made changes -
          Workflow MariaDB v3 [ 83770 ] MariaDB v4 [ 153170 ]

          People

            thiru Thirunarayanan Balathandayuthapani
            alice Alice Sherepa
            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.