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

parts.partition_special_innodb failed in buildbot with timeout

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Won't Fix
    • 10.2(EOL)
    • N/A
    • Tests, MTR
    • None

    Description

      http://buildbot.askmonty.org/buildbot/builders/kvm-zyp-sles123-amd64/builds/202

      parts.partition_special_innodb 'innodb'  w4 [ fail ]
              Test ended at 2018-07-24 16:31:41
       
      CURRENT_TEST: parts.partition_special_innodb
      mysqltest: At line 147: query 'reap' failed: 1205: Lock wait timeout exceeded; try restarting transaction
       
      The result from queries just before the failure was:
      < snip >
      Table	Op	Msg_type	Msg_text
      test.t1	check	status	OK
      connection con1;
      UNLOCK TABLES;
      connection con2;
      DROP TABLE t1;
      connection con1;
      CREATE TABLE t2 ( i INT NOT NULL AUTO_INCREMENT PRIMARY KEY, f INT )
      ENGINE = InnoDB PARTITION BY HASH(i) PARTITIONS 2;
      connection con2;
      SET lock_wait_timeout = 2;
      connection con1;
      LOCK TABLE t2 READ;
      connection con2;
      ALTER TABLE t2 ADD PARTITION PARTITIONS 2;
      ERROR HY000: Lock wait timeout exceeded; try restarting transaction
      ALTER TABLE t2 ADD PARTITION PARTITIONS 2;
      connection con1;
      UNLOCK TABLES;
      connection con2;
       
      More results from queries before failure can be found in /dev/shm/var/4/log/partition_special_innodb.log
      

      Attachments

        Activity

          People

            Unassigned Unassigned
            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.