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

main.partition_innodb2 fails in buildbot with different EXPLAIN output

Details

    • Bug
    • Status: Closed (View Workflow)
    • Blocker
    • Resolution: Fixed
    • 11.0(EOL), 11.1(EOL), 11.2(EOL)
    • 11.0.4, 11.1.3, 11.2.2
    • Tests
    • None

    Description

      preview-11.3-preview b09e99ff7

      main.partition_innodb2 'innodb'          w1 [ fail ]
              Test ended at 2023-09-17 08:51:10
       
      CURRENT_TEST: main.partition_innodb2
      --- /mnt/buildbot/build/mariadb-11.3.0/mysql-test/main/partition_innodb2.result	2023-09-17 04:23:21.000000000 -0400
      +++ /mnt/buildbot/build/mariadb-11.3.0/mysql-test/main/partition_innodb2.reject	2023-09-17 08:51:09.429117589 -0400
      @@ -18,7 +18,7 @@
       explain
       delete t1, t2 from t1, t2 where t1.a=t2.a;
       id	select_type	table	type	possible_keys	key	key_len	ref	rows	Extra
      -1	SIMPLE	t1	ALL	NULL	NULL	NULL	NULL	4	Using where
      +1	SIMPLE	t1	ALL	NULL	NULL	NULL	NULL	5	Using where
       1	SIMPLE	t2	ref	a	a	5	test.t1.a	1	
       delete t1, t2 from t1, t2 where t1.a=t2.a;
       drop table t1,t2;
       
      mysqltest: Result content mismatch
      

      Please start masking the row count in the test results if it's neither stable nor important.

      Attachments

        Activity

          Transition Time In Source Status Execution Times
          Sergei Petrunia made transition -
          Open In Progress
          2d 12h 1m 1
          Sergei Petrunia made transition -
          In Progress Closed
          25m 34s 1

          People

            psergei Sergei Petrunia
            elenst Elena Stepanova
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.