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

autoinc_debug of rocksdb test suite fails

Details

    Description

      CURRENT_TEST: rocksdb.autoinc_debug
      --- /home/sanja/maria/git/server/storage/rocksdb/mysql-test/rocksdb/r/autoinc_debug.result	2018-05-17 11:53:27.913983298 +0200
      +++ /home/sanja/maria/git/server/storage/rocksdb/mysql-test/rocksdb/r/autoinc_debug.reject	2018-05-17 13:13:59.953187229 +0200
      @@ -61,10 +61,10 @@
       ERROR HY000: Lost connection to MySQL server during query
       select table_schema, table_name, auto_increment from information_schema.tables where table_name = 't';
       table_schema	table_name	auto_increment
      -test	t	4
      +test	t	1
       select max(i) from t;
       max(i)
      -3
      +NULL
       # After engine prepare
       begin;
       insert into t values ();
      @@ -74,10 +74,10 @@
       ERROR HY000: Lost connection to MySQL server during query
       select table_schema, table_name, auto_increment from information_schema.tables where table_name = 't';
       table_schema	table_name	auto_increment
      -test	t	4
      +test	t	1
       select max(i) from t;
       max(i)
      -3
      +NULL
       # After binlog
       begin;
       insert into t values ();
      @@ -87,10 +87,10 @@
       ERROR HY000: Lost connection to MySQL server during query
       select table_schema, table_name, auto_increment from information_schema.tables where table_name = 't';
       table_schema	table_name	auto_increment
      -test	t	6
      +test	t	3
       select max(i) from t;
       max(i)
      -5
      +2
       # After everything
       begin;
       insert into t values ();
      @@ -100,8 +100,8 @@
       ERROR HY000: Lost connection to MySQL server during query
       select table_schema, table_name, auto_increment from information_schema.tables where table_name = 't';
       table_schema	table_name	auto_increment
      -test	t	8
      +test	t	5
       select max(i) from t;
       max(i)
      -7
      +4
       drop table t;
       
      mysqltest: Result length mismatch
      

      Attachments

        Activity

          Doesn't fail for me when running standalone. Fails if I run ./mtr --parallel 5 --suite rocksdb

          serg Sergei Golubchik added a comment - Doesn't fail for me when running standalone. Fails if I run ./mtr --parallel 5 --suite rocksdb

          The code for crash_commit_before:

            DBUG_EXECUTE_IF("crash_commit_before", DBUG_SUICIDE(););
          

          The state of the database after restart seems to be as if the last few transactions before the "crash_commit_before" was hit were not persisted on
          disk (playing around with the testcase confirms this).

          MariaDB runs the rocksdb testsuite with rocksdb-flush-log-at-trx-commit=0. This is a difference from the upstream. The reason for this was that this is irrelevant for most of the tests, and without this a lot of tests take unacceptably long on buildbot/other dev machines).

          psergei Sergei Petrunia added a comment - The code for crash_commit_before: DBUG_EXECUTE_IF( "crash_commit_before" , DBUG_SUICIDE();); The state of the database after restart seems to be as if the last few transactions before the "crash_commit_before" was hit were not persisted on disk (playing around with the testcase confirms this). MariaDB runs the rocksdb testsuite with rocksdb-flush-log-at-trx-commit=0 . This is a difference from the upstream. The reason for this was that this is irrelevant for most of the tests, and without this a lot of tests take unacceptably long on buildbot/other dev machines).

          People

            psergei Sergei Petrunia
            sanja Oleksandr Byelkin
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.