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

InnoDB: Assertion failure loop_count < 5 in file log0log.cc

Details

    Description

      https://internal.askmonty.org/buildbot/builders/work-amd64-valgrind/builds/9920/steps/test/logs/stdio

      2017-02-24 17:08:59 132b6700  InnoDB: Assertion failure in thread 321611520 in file log0log.cc line 1576
      InnoDB: Failing assertion: loop_count < 5
      

      Found my old upstream bug report, it's still open:
      https://bugs.mysql.com/bug.php?id=58536

      Maybe it makes sense to do something about it, at least to increase the count as suggested in the comments.

      Attachments

        Activity

          marko Marko Mäkelä added a comment - 10.0 fc673a2c121 MDEV-12127 InnoDB: Assertion failure loop_count < 5 in file log0log.cc

          ok to push, in my opinion these kinds of trivial changes do not require review.

          jplindst Jan Lindström (Inactive) added a comment - ok to push, in my opinion these kinds of trivial changes do not require review.

          MariaDB Server 10.2.2 imported a change of the limit to 128 from MySQL 5.7.9. My patch raises the limit to 100 in 10.0 and 10.1.

          The MySQL bug assignee changed the MySQL 5.7 code with a message that gives the wrong impression that no functional changes are present: "WL#6044 - Code cleanup."

          marko Marko Mäkelä added a comment - MariaDB Server 10.2.2 imported a change of the limit to 128 from MySQL 5.7.9. My patch raises the limit to 100 in 10.0 and 10.1. The MySQL bug assignee changed the MySQL 5.7 code with a message that gives the wrong impression that no functional changes are present: "WL#6044 - Code cleanup."

          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.