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

rocksdb.perf_context failed in buildbot with wrong result

    XMLWordPrintable

Details

    Description

      http://buildbot.askmonty.org/buildbot/builders/kvm-deb-stretch-amd64/builds/5075

      rocksdb.perf_context 'write_committed'   w2 [ fail ]
              Test ended at 2018-09-15 16:19:23
       
      CURRENT_TEST: rocksdb.perf_context
      --- /usr/share/mysql/mysql-test/plugin/rocksdb/rocksdb/r/perf_context.result	2018-09-15 14:56:13.000000000 -0400
      +++ /dev/shm/var/2/log/perf_context.reject	2018-09-15 16:19:23.475509292 -0400
      @@ -170,7 +170,7 @@
       SELECT COUNT(*) from INFORMATION_SCHEMA.ROCKSDB_PERF_CONTEXT_GLOBAL
       WHERE STAT_TYPE = 'IO_WRITE_NANOS' AND VALUE > 0;
       COUNT(*)
      -1
      +0
       SELECT VALUE INTO @a from INFORMATION_SCHEMA.ROCKSDB_PERF_CONTEXT_GLOBAL
       WHERE STAT_TYPE = 'IO_WRITE_NANOS';
       INSERT INTO t2 VALUES (5), (6), (7), (8);
      @@ -179,12 +179,12 @@
       AND STAT_TYPE = 'IO_WRITE_NANOS'
       AND VALUE > 0;
       COUNT(*)
      -1
      +0
       SELECT VALUE INTO @b from INFORMATION_SCHEMA.ROCKSDB_PERF_CONTEXT_GLOBAL
       WHERE STAT_TYPE = 'IO_WRITE_NANOS';
       SELECT CASE WHEN @b - @a > 0 THEN 'true' ELSE 'false' END;
       CASE WHEN @b - @a > 0 THEN 'true' ELSE 'false' END
      -true
      +false
       DROP TABLE t1;
       DROP TABLE t2;
       SET GLOBAL rocksdb_perf_context_level = @prior_rocksdb_perf_context_level;
       
      mysqltest: Result length mismatch
      

      Attachments

        Activity

          People

            psergei Sergei Petrunia
            elenst Elena Stepanova
            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.