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

innodb.innodb_mysql fails sporadically in BB

    XMLWordPrintable

    Details

      Description

      In July and 1th -18th August 2019, it happened only in 10.4/10.5-based trees.

      The failure looks like this:

      innodb.innodb_mysql 'innodb'             w2 [ fail ]
              Test ended at 2019-07-28 17:33:47
       
      CURRENT_TEST: innodb.innodb_mysql
      --- /mnt/buildbot/build/mariadb-10.4.7/mysql-test/suite/innodb/r/innodb_mysql.result	2019-07-28 07:49:28.000000000 -0400
      +++ /mnt/buildbot/build/mariadb-10.4.7/mysql-test/suite/innodb/r/innodb_mysql.reject	2019-07-28 17:33:46.613429422 -0400
      @@ -394,7 +394,7 @@
       # Masking (#) number in "rows" column of the following EXPLAIN output, as it may vary (bug#47746).
       EXPLAIN SELECT DISTINCT t1.name, t1.dept FROM t1 WHERE t1.name='rs5';
       id	select_type	table	type	possible_keys	key	key_len	ref	rows	Extra
      -1	SIMPLE	t1	range	name	name	44	NULL	#	Using where; Using index for group-by
      +1	SIMPLE	t1	ref	name	name	22	const	#	Using where; Using index
       SELECT DISTINCT t1.name, t1.dept FROM t1 WHERE t1.name='rs5';
       name	dept
       DROP TABLE t1;
       
      mysqltest: Result length mismatch
       
       - skipping '/mnt/buildbot/build/mariadb-10.4.7/mysql-test/var/2/log/innodb.innodb_mysql-innodb/'
      worker[2] > Restart  - not started
      

      the second failure pattern is:

      CURRENT_TEST: innodb.innodb_mysql
      --- /home/psergey/dev-git/10.4-rel/mysql-test/suite/innodb/r/innodb_mysql.result        2019-08-18 16:35:19.017153458 +0300
      +++ /home/psergey/dev-git/10.4-rel/mysql-test/suite/innodb/r/innodb_mysql.reject        2019-08-18 16:52:26.506107962 +0300
      @@ -3180,7 +3180,7 @@
       (SELECT * FROM t1 FORCE INDEX (idx,PRIMARY)
       WHERE a BETWEEN 2 AND 7 OR pk=1000000) AS t;
       id     select_type     table   type    possible_keys   key     key_len ref     rows    Extra
      -1      PRIMARY <derived2>      ALL     NULL    NULL    NULL    NULL    1537
      +1      PRIMARY <derived2>      ALL     NULL    NULL    NULL    NULL    1536
       2      DERIVED t1      index_merge     PRIMARY,idx     idx,PRIMARY     5,4     NULL    1537    Using sort_union(idx,PRIMARY); Using where
       SELECT COUNT(*) FROM
       (SELECT * FROM t1 FORCE INDEX (idx,PRIMARY)
       
      mysqltest: Result content mismatch
      

      Both failures occur randomly, are not common (every 10th run? 20th run?)

        Attachments

          Activity

            People

            Assignee:
            psergei Sergei Petrunia
            Reporter:
            psergei Sergei Petrunia
            Votes:
            0 Vote for this issue
            Watchers:
            1 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.