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

rpl.rpl_semi_sync_after_sync, rpl.rpl_semi_sync_after_sync_row failed in buildbot with wrong result

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Duplicate
    • 10.1, 10.2
    • N/A
    • Replication, Tests
    • None

    Description

      http://buildbot.askmonty.org/buildbot/builders/kvm-deb-jessie-amd64/builds/2858/steps/mtr/logs/stdio

      rpl.rpl_semi_sync_after_sync_row 'innodb_plugin,row' w1 [ fail ]
              Test ended at 2017-09-27 10:09:42
       
      CURRENT_TEST: rpl.rpl_semi_sync_after_sync_row
      --- /usr/share/mysql/mysql-test/suite/rpl/r/rpl_semi_sync_after_sync_row.result	2017-09-27 08:07:47.000000000 -0400
      +++ /dev/shm/var/1/log/rpl_semi_sync_after_sync_row.reject	2017-09-27 10:09:41.559456813 -0400
      @@ -228,7 +228,7 @@
       [ master status should be ON again after slave catches up ]
       show status like 'Rpl_semi_sync_master_status';
       Variable_name	Value
      -Rpl_semi_sync_master_status	ON
      +Rpl_semi_sync_master_status	OFF
       show status like 'Rpl_semi_sync_master_no_tx';
       Variable_name	Value
       Rpl_semi_sync_master_no_tx	12
       
      mysqltest: Result length mismatch
      

      Attachments

        Issue Links

          Activity

            People

              Elkin Andrei Elkin
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              2 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.