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

Details

    • Bug
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Duplicate
    • 10.1(EOL), 10.2(EOL)
    • 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

            rpl.rpl_semi_sync_after_sync
            http://buildbot.askmonty.org/buildbot/builders/kvm-deb-trusty-amd64/builds/8295/steps/mtr/logs/stdio

            rpl.rpl_semi_sync_after_sync 'innodb_plugin,stmt' w4 [ fail ]
                    Test ended at 2017-11-22 00:28:25
             
            CURRENT_TEST: rpl.rpl_semi_sync_after_sync
            --- /usr/share/mysql/mysql-test/suite/rpl/r/rpl_semi_sync_after_sync.result	2017-11-21 21:30:53.000000000 +0000
            +++ /run/shm/var/4/log/rpl_semi_sync_after_sync.reject	2017-11-22 00:28:25.443781258 +0000
            @@ -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
            @@ -250,10 +250,10 @@
             [ Semi-sync master status variables before FLUSH STATUS ]
             SHOW STATUS LIKE 'Rpl_semi_sync_master_no_tx';
             Variable_name	Value
            -Rpl_semi_sync_master_no_tx	12
            +Rpl_semi_sync_master_no_tx	13
             SHOW STATUS LIKE 'Rpl_semi_sync_master_yes_tx';
             Variable_name	Value
            -Rpl_semi_sync_master_yes_tx	17
            +Rpl_semi_sync_master_yes_tx	16
             FLUSH NO_WRITE_TO_BINLOG STATUS;
             [ Semi-sync master status variables after FLUSH STATUS ]
             SHOW STATUS LIKE 'Rpl_semi_sync_master_no_tx';
             
            mysqltest: Result length mismatch
            

            elenst Elena Stepanova added a comment - rpl.rpl_semi_sync_after_sync http://buildbot.askmonty.org/buildbot/builders/kvm-deb-trusty-amd64/builds/8295/steps/mtr/logs/stdio rpl.rpl_semi_sync_after_sync 'innodb_plugin,stmt' w4 [ fail ] Test ended at 2017-11-22 00:28:25   CURRENT_TEST: rpl.rpl_semi_sync_after_sync --- /usr/share/mysql/mysql-test/suite/rpl/r/rpl_semi_sync_after_sync.result 2017-11-21 21:30:53.000000000 +0000 +++ /run/shm/var/4/log/rpl_semi_sync_after_sync.reject 2017-11-22 00:28:25.443781258 +0000 @@ -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 @@ -250,10 +250,10 @@ [ Semi-sync master status variables before FLUSH STATUS ] SHOW STATUS LIKE 'Rpl_semi_sync_master_no_tx'; Variable_name Value -Rpl_semi_sync_master_no_tx 12 +Rpl_semi_sync_master_no_tx 13 SHOW STATUS LIKE 'Rpl_semi_sync_master_yes_tx'; Variable_name Value -Rpl_semi_sync_master_yes_tx 17 +Rpl_semi_sync_master_yes_tx 16 FLUSH NO_WRITE_TO_BINLOG STATUS; [ Semi-sync master status variables after FLUSH STATUS ] SHOW STATUS LIKE 'Rpl_semi_sync_master_no_tx';   mysqltest: Result length mismatch
            alice Alice Sherepa added a comment - - edited

            on 10.3 http://buildbot.askmonty.org/buildbot/builders/kvm-rpm-centos73-ppc64/builds/14178/steps/mtr/logs/stdio

            rpl.rpl_semi_sync_after_sync_row 'innodb,row' w4 [ fail ]
                    Test ended at 2020-09-02 04:52:35
             
            CURRENT_TEST: rpl.rpl_semi_sync_after_sync_row
            --- /usr/share/mysql-test/suite/rpl/r/rpl_semi_sync_after_sync_row.result	2020-09-01 23:36:18.000000000 +0000
            +++ /dev/shm/var/4/log/rpl_semi_sync_after_sync_row.reject	2020-09-02 04:52:34.560071145 +0000
            @@ -407,7 +407,7 @@
             [ Semi-sync status on master should be ON ]
             show status like 'Rpl_semi_sync_master_clients';
             Variable_name	Value
            -Rpl_semi_sync_master_clients	0
            +Rpl_semi_sync_master_clients	1
             show status like 'Rpl_semi_sync_master_status';
             Variable_name	Value
             Rpl_semi_sync_master_status	ON
             
            mysqltest: Result content mismatch
            

            alice Alice Sherepa added a comment - - edited on 10.3 http://buildbot.askmonty.org/buildbot/builders/kvm-rpm-centos73-ppc64/builds/14178/steps/mtr/logs/stdio rpl.rpl_semi_sync_after_sync_row 'innodb,row' w4 [ fail ] Test ended at 2020-09-02 04:52:35   CURRENT_TEST: rpl.rpl_semi_sync_after_sync_row --- /usr/share/mysql-test/suite/rpl/r/rpl_semi_sync_after_sync_row.result 2020-09-01 23:36:18.000000000 +0000 +++ /dev/shm/var/4/log/rpl_semi_sync_after_sync_row.reject 2020-09-02 04:52:34.560071145 +0000 @@ -407,7 +407,7 @@ [ Semi-sync status on master should be ON ] show status like 'Rpl_semi_sync_master_clients'; Variable_name Value -Rpl_semi_sync_master_clients 0 +Rpl_semi_sync_master_clients 1 show status like 'Rpl_semi_sync_master_status'; Variable_name Value Rpl_semi_sync_master_status ON   mysqltest: Result content mismatch

            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.