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

rpl.rpl_semi_sync, rpl.rpl_semi_sync_after_sync_row fail in buildbot

    Details

      Description

      http://buildbot.askmonty.org/buildbot/builders/kvm-bintar-quantal-x86/builds/1562/steps/test/logs/stdio

      rpl.rpl_semi_sync 'mix,xtradb'           w3 [ fail ]
              Test ended at 2014-12-29 16:25:08
       
      CURRENT_TEST: rpl.rpl_semi_sync
      --- /usr/local/mariadb-10.1.3-linux-i686/mysql-test/suite/rpl/r/rpl_semi_sync.result	2014-12-29 13:44:34.000000000 +0200
      +++ /usr/local/mariadb-10.1.3-linux-i686/mysql-test/suite/rpl/r/rpl_semi_sync.reject	2014-12-29 16:25:08.291372070 +0200
      @@ -161,10 +161,10 @@
       Rpl_semi_sync_master_status	ON
       show status like 'Rpl_semi_sync_master_no_tx';
       Variable_name	Value
      -Rpl_semi_sync_master_no_tx	0
      +Rpl_semi_sync_master_no_tx	1
       show status like 'Rpl_semi_sync_master_yes_tx';
       Variable_name	Value
      -Rpl_semi_sync_master_yes_tx	14
      +Rpl_semi_sync_master_yes_tx	13
       show status like 'Rpl_semi_sync_master_clients';
       Variable_name	Value
       Rpl_semi_sync_master_clients	1
      @@ -176,10 +176,10 @@
       Rpl_semi_sync_master_status	OFF
       show status like 'Rpl_semi_sync_master_no_tx';
       Variable_name	Value
      -Rpl_semi_sync_master_no_tx	1
      +Rpl_semi_sync_master_no_tx	2
       show status like 'Rpl_semi_sync_master_yes_tx';
       Variable_name	Value
      -Rpl_semi_sync_master_yes_tx	14
      +Rpl_semi_sync_master_yes_tx	13
       delete from t1 where a=10;
       delete from t1 where a=9;
       delete from t1 where a=8;
      @@ -197,10 +197,10 @@
       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
      +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	14
      +Rpl_semi_sync_master_yes_tx	13
       #
       # Test semi-sync status on master will be ON again when slave catches up
       #
      @@ -230,10 +230,10 @@
       Rpl_semi_sync_master_status	ON
       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	14
      +Rpl_semi_sync_master_yes_tx	13
       show status like 'Rpl_semi_sync_master_clients';
       Variable_name	Value
       Rpl_semi_sync_master_clients	1
      @@ -249,10 +249,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	15
      +Rpl_semi_sync_master_yes_tx	14
       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 content mismatch

      It fails in different ways, for example here is what I got running it separately on my local machine:

      CURRENT_TEST: rpl.rpl_semi_sync
      --- /data/repo/git/10.1/mysql-test/suite/rpl/r/rpl_semi_sync.result	2014-12-12 04:38:33.000000000 +0400
      +++ /data/repo/git/10.1/mysql-test/suite/rpl/r/rpl_semi_sync.reject	2014-12-29 20:54:05.000000000 +0400
      @@ -249,10 +249,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	15
      +Rpl_semi_sync_master_yes_tx	14
       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 content mismatch

      According to cross-reference, it started failing massively from this push:
      http://buildbot.askmonty.org/buildbot/builders/work-amd64-valgrind/builds/6522

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                knielsen Kristian Nielsen
                Reporter:
                elenst Elena Stepanova
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: