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

rpl.rpl_upgrade_master_info fails sporadically in buildbot

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.2(EOL)
    • 10.2.10
    • Tests
    • None
    • 10.2.4-2

    Description

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

      rpl.rpl_upgrade_master_info 'stmt'       w3 [ fail ]  Found warnings/errors in server log file!
              Test ended at 2016-12-21 04:28:40
      line
      2016-12-21  4:28:23 1328198976 [ERROR] mysqld: Table './mysql/gtid_slave_pos' is marked as crashed and should be repaired
      2016-12-21  4:28:23 1328198976 [Warning] Checking table:   './mysql/gtid_slave_pos'
      2016-12-21  4:28:23 1328198976 [ERROR] mysql.gtid_slave_pos: 1 client is using or hasn't closed the table properly
      2016-12-21  4:28:24 1329714496 [ERROR] mysqld: Table './test/t1' is marked as crashed and should be repaired
      2016-12-21  4:28:24 1329714496 [Warning] Checking table:   './test/t1'
      2016-12-21  4:28:24 1329714496 [ERROR] test.t1: 1 client is using or hasn't closed the table properly
      ^ Found warnings in /usr/local/mariadb-10.2.3-linux-x86_64/mysql-test/var/3/log/mysqld.2.err
      ok
       
       - skipping '/usr/local/mariadb-10.2.3-linux-x86_64/mysql-test/var/3/log/rpl.rpl_upgrade_master_info-stmt/'
       
      Retrying test rpl.rpl_upgrade_master_info, attempt(2/3)...
      

      Attachments

        Issue Links

          Activity

            People

              monty Michael Widenius
              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.