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

rpl.rpl_parallel_optimistic_nobinlog failed in buildbot with "InnoDB: Killing connection failed Deadlock"

Details

    • 10.2.4-1

    Description

      http://buildbot.askmonty.org/buildbot/builders/kvm-deb-trusty-amd64/builds/4069/steps/test_5/logs/stdio

      rpl.rpl_parallel_optimistic_nobinlog 'stmt,xtradb' w1 [ fail ]  Found warnings/errors in server log file!
      		 
              Test ended at 2016-11-29 17:27:17
      		 
      line
      		 
      2016-11-29 17:27:17 140288030135040 [Warning] InnoDB: Killing connection failed Deadlock(16)
      		 
      ^ Found warnings in /run/shm/var/1/log/mysqld.2.err
      		 
      ok
      		 
       
      		 
       - saving '/run/shm/var/1/log/rpl.rpl_parallel_optimistic_nobinlog-stmt,xtradb/' to '/run/shm/var/log/rpl.rpl_parallel_optimistic_nobinlog-stmt,xtradb/'
      		 
       
      		 
      Retrying test rpl.rpl_parallel_optimistic_nobinlog, attempt(2/3)...

      Attachments

        Issue Links

          relates to

          Task - A task that needs to be done. MDEV-7069 Fix buildbot failures in main server trees

          • Major - Major loss of function.
          • Stalled

          Activity

            Ascending order - Click to sort in descending order
            elenst Elena Stepanova created issue -
            elenst Elena Stepanova made changes -
            Field Original Value New Value
            ratzpo Rasmus Johansson (Inactive) made changes -
            Sprint 10.2.4-1 [ 121 ]
            ratzpo Rasmus Johansson (Inactive) made changes -
            Rank Ranked lower
            marko Marko Mäkelä made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            marko Marko Mäkelä added a comment -

            This turned out to be a bogus warning message for the rare case that the transaction that is subject to KILL QUERY has already been aborted due to a deadlock.

            marko Marko Mäkelä added a comment - This turned out to be a bogus warning message for the rare case that the transaction that is subject to KILL QUERY has already been aborted due to a deadlock.
            marko Marko Mäkelä made changes -
            Assignee Marko Mäkelä [ marko ] Jan Lindström [ jplindst ]
            Status In Progress [ 3 ] In Review [ 10002 ]
            marko Marko Mäkelä made changes -
            Affects Version/s 10.2.2 [ 22013 ]
            Affects Version/s 10.2 [ 14601 ]
            marko Marko Mäkelä made changes -
            Fix Version/s 10.2.3 [ 22115 ]
            Fix Version/s 10.2 [ 14601 ]
            jplindst Jan Lindström (Inactive) added a comment -

            ok to push.

            jplindst Jan Lindström (Inactive) added a comment - ok to push.
            jplindst Jan Lindström (Inactive) made changes -
            Assignee Jan Lindström [ jplindst ] Marko Mäkelä [ marko ]
            Status In Review [ 10002 ] Stalled [ 10000 ]
            marko Marko Mäkelä made changes -
            issue.field.resolutiondate 2016-12-08 15:24:22.0 2016-12-08 15:24:22.259
            marko Marko Mäkelä made changes -
            Resolution Fixed [ 1 ]
            Status Stalled [ 10000 ] Closed [ 6 ]
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 78533 ] MariaDB v4 [ 151272 ]

            People

              marko Marko Mäkelä
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              3 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.