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

gcol.gcol_rollback failed in buildbot with Unknown storage engine 'InnoDB'

Details

    Description

      Note: possibly related to MDEV-16273 and/or 12905.

      http://buildbot.askmonty.org/buildbot/builders/kvm-bintar-centos6-amd64-debug/builds/691

      gcol.gcol_rollback 'innodb'              w3 [ fail ]
              Test ended at 2018-08-10 17:22:44
       
      CURRENT_TEST: gcol.gcol_rollback
      mysqltest: At line 36: query 'SELECT * FROM t' failed: 1286: Unknown storage engine 'InnoDB'
       
      The result from queries just before the failure was:
      < snip >
      DELETE FROM t where a = 12;
      ROLLBACK TO SAVEPOINT a;
      COMMIT;
      CHECK TABLE t;
      Table	Op	Msg_type	Msg_text
      test.t	check	status	OK
      SELECT * FROM t;
      a	b
      9	9
      BEGIN;
      INSERT INTO t (a) VALUES (10);
      SELECT * FROM t;
      

      Attachments

        Issue Links

          Activity

            Possibly fixed by the next commit

            commit 29150e23912ef6e1fe386f53b778c9a5551c4790 b853b4fd88b441f36eeb7eabdce79918ef10538a
            Author: Marko Mäkelä <marko.makela@mariadb.com>
            Date:   Fri Aug 10 17:01:53 2018 +0300
             
                Revert part of b853b4fd88b441f36eeb7eabdce79918ef10538a
                
                recv_parse_log_recs(): Do not check for corruption before
                checking for end-of-log-buffer. For some reason, adding the
                check to the logical-looking place would cause intermittent
                recovery failures in the tests innodb.innodb-index and
                innodb_gis.rtree_compress2.
            

            elenst Elena Stepanova added a comment - Possibly fixed by the next commit commit 29150e23912ef6e1fe386f53b778c9a5551c4790 b853b4fd88b441f36eeb7eabdce79918ef10538a Author: Marko Mäkelä <marko.makela@mariadb.com> Date: Fri Aug 10 17:01:53 2018 +0300   Revert part of b853b4fd88b441f36eeb7eabdce79918ef10538a recv_parse_log_recs(): Do not check for corruption before checking for end-of-log-buffer. For some reason, adding the check to the logical-looking place would cause intermittent recovery failures in the tests innodb.innodb-index and innodb_gis.rtree_compress2.

            I don't see any failure of gcol.gcol_rollback in cross-reference after 2018-08-10. I would like to close this bug. Looks like the following patch fixed the issue:

            commit 29150e23912ef6e1fe386f53b778c9a5551c4790 b853b4fd88b441f36eeb7eabdce79918ef10538a
             
            Author: Marko Mäkelä <marko.makela@mariadb.com>
            Date:   Fri Aug 10 17:01:53 2018 +0300
             
            Revert part of b853b4fd88b441f36eeb7eabdce79918ef10538a
                
            

            thiru Thirunarayanan Balathandayuthapani added a comment - - edited I don't see any failure of gcol.gcol_rollback in cross-reference after 2018-08-10. I would like to close this bug. Looks like the following patch fixed the issue: commit 29150e23912ef6e1fe386f53b778c9a5551c4790 b853b4fd88b441f36eeb7eabdce79918ef10538a   Author: Marko Mäkelä <marko.makela@mariadb.com> Date: Fri Aug 10 17:01:53 2018 +0300   Revert part of b853b4fd88b441f36eeb7eabdce79918ef10538a

            People

              thiru Thirunarayanan Balathandayuthapani
              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.