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

rocksdb.rocksdb fails: line 1117: query 'reap' succeeded - should have failed

Details

    Description

      rocksdb.rocksdb test currently fails like this (note that it had several different kinds of failures):

      http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest/builds/10764/steps/test_2/logs/stdio

      rocksdb.rocksdb                          w1 [ fail ]
              Test ended at 2017-10-27 14:23:42
       
      CURRENT_TEST: rocksdb.rocksdb
      mysqltest: At line 1117: query 'reap' succeeded - should have failed with errno 1317...
       
      The result from queries just before the failure was:
      < snip >
      pk
      affected rows: 0
      DROP TABLE t1,t2;
      #
      # MDEV-4374: RocksDB: Valgrind warnings 'Use of uninitialised value' on 
      #   inserting into a varchar column
      #
      CREATE TABLE t1 (pk INT PRIMARY KEY, a VARCHAR(32)) ENGINE=RocksDB;
      INSERT INTO t1 VALUES (1,'foo'),(2,'bar');
      DROP TABLE t1;
      #
      # MDEV-4061: RocksDB: Changes from an interrupted query are still applied
      

      Another similar failure:
      http://buildbot.askmonty.org/buildbot/builders/kvm-bintar-trusty-amd64/builds/3267/steps/test/logs/stdio

      This happens very often in buildbot, although all attempts to reproduce have not been successful.

      Attachments

        Issue Links

          Activity

            Transition Time In Source Status Execution Times
            Sergei Petrunia made transition -
            Open Closed
            1d 2h 55m 1

            People

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