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

rpl.rpl_gtid_stop_start fails sporadically in buildbot

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 10.2
    • Fix Version/s: 10.2.10
    • Component/s: Tests
    • Labels:
      None
    • Sprint:
      10.2.4-2

      Description

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

      rpl.rpl_gtid_stop_start 'innodb,row'     w1 [ fail ]
              Test ended at 2016-12-21 04:28:24
       
      CURRENT_TEST: rpl.rpl_gtid_stop_start
      --- /usr/local/mariadb-10.2.3-linux-x86_64/mysql-test/suite/rpl/r/rpl_gtid_stop_start.result	2016-12-20 21:52:34.000000000 +0100
      +++ /usr/local/mariadb-10.2.3-linux-x86_64/mysql-test/suite/rpl/r/rpl_gtid_stop_start.reject	2016-12-21 04:28:24.000000000 +0100
      @@ -108,6 +108,10 @@
       5
       6
       7
      +Warnings:
      +Error	145	Table './test/t1' is marked as crashed and should be repaired
      +Error	1194	Table 't1' is marked as crashed and should be repaired
      +Error	1034	1 client is using or hasn't closed the table properly
       *** MDEV-4486: Allow to start old-style replication even if mysql.gtid_slave_pos is unavailable
       connection server_2;
       include/stop_slave.inc
       
      mysqltest: Result length mismatch
      

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                monty Michael Widenius
                Reporter:
                elenst Elena Stepanova
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: