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

rpl.rpl_semi_sync_uninstall_plugin fails in bb with "Found wrong usage of mutex 'LOCK_thd_kill' and 'LOCK_show_status'"

    XMLWordPrintable

Details

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

    Description

      http://buildbot.askmonty.org/buildbot/builders/kvm-bintar-centos6-amd64-debug/builds/3320/steps/mtr/logs/stdio

      rpl.rpl_semi_sync_uninstall_plugin 'stmt' w2 [ fail ]  Found warnings/errors in server log file!
      		 
              Test ended at 2021-01-08 18:12:41
      		 
      line
      		 
      safe_mutex: Found wrong usage of mutex 'LOCK_thd_kill' and 'LOCK_show_status'
      		 
      ^ Found warnings in /usr/local/mariadb-10.2.37-linux-x86_64/mysql-test/var/2/log/mysqld.2.err
      		 
      ok

      the test was failing before with a crash MDEV-7140 (after the fix of MDEV-23536 the test fails as described above)

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-7140 Sporadic buildbot failures in rpl.rpl_semi_sync_uninstall_plugin, 2013: 'Lost connection to MySQL server

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-23536 Race condition between KILL and transaction commit

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            People

              Unassigned Unassigned
              alice Alice Sherepa
              Votes:
              0 Vote for this issue
              Watchers:
              4 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.