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

rpl.rpl_skip_replication, rpl.rpl_set_statement_default_master failed in buildbot

    XMLWordPrintable

Details

    Description

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

      rpl.rpl_skip_replication 'innodb,mix'    w4 [ fail ]  Found warnings/errors in server log file!
              Test ended at 2017-06-30 23:17:54
      line
      2017-06-30 23:17:53 2792700736 [Warning] Master is configured to log replication events with checksum, but will not send such events to slaves that cannot process them
      ^ Found warnings in /run/shm/var/4/log/mysqld.1.err
      ok
      

      http://buildbot.askmonty.org/buildbot/builders/kvm-bintar-centos5-amd64/builds/5711/steps/test/logs/stdio

      rpl.rpl_set_statement_default_master 'mix' w2 [ fail ]  Found warnings/errors in server log file!
              Test ended at 2017-07-08 12:43:39
      line
      2017-07-08 12:43:39 1075878208 [Warning] Master is configured to log replication events with checksum, but will not send such events to slaves that cannot process them
      ^ Found warnings in /usr/local/mariadb-10.2.7-linux-x86_64/mysql-test/var/2/log/mysqld.1.err
      ok
       
       - saving '/usr/local/mariadb-10.2.7-linux-x86_64/mysql-test/var/2/log/rpl.rpl_set_statement_default_master-mix/' to '/usr/local/mariadb-10.2.7-linux-x86_64/mysql-test/var/log/rpl.rpl_set_statement_default_master-mix/'
      

      Attachments

        Issue Links

          Activity

            People

              sujatha.sivakumar Sujatha Sivakumar (Inactive)
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              6 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.