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

main.tc_heuristic_recover failed in buildbot with wrong error on mysqld_stub_cmd

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.0
    • None
    • Tests
    • None

    Description

      http://buildbot.askmonty.org/buildbot/builders/win32-debug/builds/7348/steps/test/logs/stdio

      main.tc_heuristic_recover 'xtradb'       w2 [ fail ]
              Test ended at 2018-02-01 15:27:07
       
      CURRENT_TEST: main.tc_heuristic_recover
      mysqltest: In included file "D:/win32-debug/build/src/mysql-test/include/fail_start_mysqld.inc": 
      included from D:/win32-debug/build/src/mysql-test/t/tc_heuristic_recover.test at line 60:
      At line 15: command "$mysqld_stub_cmd $restart_parameters >> $error_log  2>&1" failed with wrong error: 3
       
      The result from queries just before the failure was:
      < snip >
      set debug_sync='RESET';
      CREATE TABLE t1 (i INT) ENGINE=InnoDB;
      SET GLOBAL innodb_flush_log_at_trx_commit=1;
      FLUSH TABLES;
      set debug_sync='ha_commit_trans_after_prepare WAIT_FOR go';
      INSERT INTO t1 VALUES (1);;
      # Prove that no COMMIT or ROLLBACK occurred yet.
      SELECT * FROM t1;
      i
      SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED;
      SELECT * FROM t1;
      i
      1
      # Kill the server
       
      More results from queries before failure can be found in D:\win32-debug\build\mysql-test\var\2\log\tc_heuristic_recover.log
       
       - saving 'D:/win32-debug/build/mysql-test/var/2/log/main.tc_heuristic_recover-xtradb/' to 'D:/win32-debug/build/mysql-test/var/log/main.tc_heuristic_recover-xtradb/'
       
      Retrying test main.tc_heuristic_recover, attempt(2/3)...
       
      ***Warnings generated in error logs during shutdown after running tests: main.tc_heuristic_recover main.sp_trans_log
       
      180201 15:27:00 [ERROR] Found 1 prepared transactions! It means that mysqld was not shut down properly last time and critical recovery information (last binlog or tc.log file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions.
      180201 15:27:00 [ERROR] Aborting
      abort() has been called180201 15:27:01 [ERROR] mysqld got exception 0x80000003 ;
      Attempting backtrace. You can use the following information to find out
      

      Attachments

        Activity

          People

            Unassigned Unassigned
            elenst Elena Stepanova
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.