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

innodb.deadlock_detect failed in buildbot

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 10.2
    • Fix Version/s: 10.3.4, 10.2.13
    • Component/s: Tests
    • Labels:
      None

      Description

      http://buildbot.askmonty.org/buildbot/builders/kvm-deb-wheezy-x86/builds/4832/steps/mtr/logs/stdio

      innodb.deadlock_detect 'innodb'          w4 [ fail ]
              Test ended at 2017-07-04 08:46:49
       
      CURRENT_TEST: innodb.deadlock_detect
      mysqltest: At line 44: query 'reap' succeeded - should have failed with errno 1205...
       
      The result from queries just before the failure was:
      < snip >
      id	INT,
      PRIMARY KEY(id)
      ) ENGINE=InnoDB;
      INSERT INTO t1 VALUES(1), (2), (3);
      BEGIN;
      SELECT * FROM t1 WHERE id = 1 FOR UPDATE;
      id
      1
      connect  con1,localhost,root,,;
      BEGIN;
      SELECT * FROM t1 WHERE id = 2 FOR UPDATE;
      id
      2
      SELECT * FROM t1 WHERE id = 1 FOR UPDATE;
      connection default;
      SELECT * FROM t1 WHERE id = 2 FOR UPDATE;
      connection con1;
      ERROR HY000: Lock wait timeout exceeded; try restarting transaction
      ROLLBACK;
      connection default;
       
      More results from queries before failure can be found in /run/shm/var/4/log/deadlock_detect.log
      

        Attachments

          Activity

            People

            Assignee:
            jplindst Jan Lindström
            Reporter:
            elenst Elena Stepanova
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: