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

main.order_by_optimizer_innodb fails in buildbot

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 10.1, 10.4
    • Fix Version/s: 10.1
    • Component/s: Tests
    • Labels:
      None

      Description

      http://buildbot.askmonty.org/buildbot/builders/kvm-deb-sid-x86/builds/2000/steps/test_5/logs/stdio

      main.order_by_optimizer_innodb 'xtradb'  w1 [ fail ]
              Test ended at 2016-07-03 04:07:35
       
      CURRENT_TEST: main.order_by_optimizer_innodb
      --- /usr/share/mysql/mysql-test/r/order_by_optimizer_innodb.result	2016-07-03 02:45:44.000000000 -0400
      +++ /dev/shm/var/1/log/order_by_optimizer_innodb.reject	2016-07-03 04:07:35.159355291 -0400
      @@ -40,7 +40,7 @@
       # The following should use range(ux_pk1_fd5), two key parts (key_len=5+8=13)
       EXPLAIN SELECT * FROM t2 USE INDEX(ux_pk1_fd5) WHERE pk1=9 AND fd5 < 500 ORDER BY fd5 DESC LIMIT 10;
       id	select_type	table	type	possible_keys	key	key_len	ref	rows	Extra
      -1	SIMPLE	t2	range	ux_pk1_fd5	ux_pk1_fd5	13	NULL	137	Using where
      +1	SIMPLE	t2	ref	ux_pk1_fd5	ux_pk1_fd5	4	const	137	Using where
       # This also must use range, not ref. key_len must be 13
       EXPLAIN SELECT * FROM t2                       WHERE pk1=9 AND fd5 < 500 ORDER BY fd5 DESC LIMIT 10;
       id	select_type	table	type	possible_keys	key	key_len	ref	rows	Extra
       
      mysqltest: Result length mismatch
      

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                psergey Sergei Petrunia
                Reporter:
                elenst Elena Stepanova
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated: