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

rpl.rpl_semi_sync_event_after_sync 'fails if there is no semisync plugin

Details

    Description

      rpl.rpl_semi_sync_event_after_sync 'mix,xtradb' [ fail ]
              Test ended at 2017-01-21 16:54:15
       
      CURRENT_TEST: rpl.rpl_semi_sync_event_after_sync
      mysqltest: At line 1: query 'set global rpl_semi_sync_master_wait_point=AFTER_SYNC' failed: 1193: Unknown system variable 'rpl_semi_sync_master_wait_point'
       
      The result from queries just before the failure was:
      set global rpl_semi_sync_master_wait_point=AFTER_SYNC;
      

      The test first attempts to set rpl_semi_sync_master_wait_point and then sources rpl_semi_sync_event.test which, in turn, sources include/have_semisync.inc which checks whether the plugin exists.

      The easy way to fix it is to source include/have_semisync.inc from rpl_semi_sync_event_after_sync itself. There might be smarter ways to do the same.

      Attachments

        Activity

          alice

          Please do whatever you want with it. I think 10.2 was the last version where the plugin was a library, so probably it's not even applicable to 10.3 (or maybe it is, for special builds, but MTR tests don't usually work for customized builds anyway).

          elenst Elena Stepanova added a comment - alice Please do whatever you want with it. I think 10.2 was the last version where the plugin was a library, so probably it's not even applicable to 10.3 (or maybe it is, for special builds, but MTR tests don't usually work for customized builds anyway).

          People

            alice Alice Sherepa
            elenst Elena Stepanova
            Votes:
            0 Vote for this issue
            Watchers:
            1 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.