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

main.max_statement_time fails in buildbot in different ways

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 10.1
    • Fix Version/s: 10.1.7
    • Component/s: Tests
    • Labels:
      None
    • Sprint:
      10.1.7-1, 10.1.7-2

      Description

      http://buildbot.askmonty.org/buildbot/builders/kvm-deb-debian6-x86/builds/3971/steps/test_4/logs/stdio

      main.max_statement_time 'innodb_plugin'  w4 [ fail ]
              Test ended at 2015-06-19 16:57:34
       
      CURRENT_TEST: main.max_statement_time
      mysqltest: At line 208: query 'call pr()' succeeded - should have failed with errno 1968...
       
      The result from queries just before the failure was:
      < snip >
      NULL
      SELECT RELEASE_LOCK('lock');
      RELEASE_LOCK('lock')
      1
      DROP TABLE t1;
      #
      # MDEV-7011:MAX_STATEMENT_TIME has no effect in a procedure after
      # a previous successful statement
      #
      create table t1 (i int);
      insert into t1 values (1),(2),(3),(4);
      insert into t1 select a.* from t1 a, t1 b, t1 c, t1 d, t1 e, t1 f, t1 g;
      create procedure pr()
      begin
      select 1;
      select sql_no_cache * from t1 where i > 5;
      select sql_no_cache * from t1 where i > 5;
      end |
      set max_statement_time = 0.001;
      call pr();

      http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest/builds/4469/steps/test_6/logs/stdio

      main.max_statement_time 'innodb_plugin'  w4 [ fail ]
              Test ended at 2015-06-19 17:55:53
       
      CURRENT_TEST: main.max_statement_time
      --- /mnt/buildbot/build/mariadb-10.1.5/mysql-test/r/max_statement_time.result	2015-06-19 14:10:56.000000000 +0300
      +++ /mnt/buildbot/build/mariadb-10.1.5/mysql-test/r/max_statement_time.reject	2015-06-19 17:55:53.000000000 +0300
      @@ -164,6 +164,7 @@
       call pr();
       1
       1
      +i
       ERROR 70100: Query execution was interrupted (max_statement_time exceeded)
       drop procedure pr;
       create procedure pr()
      @@ -173,6 +174,7 @@
       end |
       set max_statement_time = 0.001;
       call pr();
      +i
       ERROR 70100: Query execution was interrupted (max_statement_time exceeded)
       set max_statement_time = 0;
       drop procedure pr;
       
      mysqltest: Result length mismatch

      http://buildbot.askmonty.org/buildbot/builders/kvm-bintar-centos5-amd64/builds/1511/steps/test/logs/stdio
      (I got this one locally, too)

      main.max_statement_time 'xtradb'         w1 [ fail ]
              Test ended at 2015-06-19 15:06:29
       
      CURRENT_TEST: main.max_statement_time
      mysqltest: At line 209: query 'drop procedure pr' failed: 1968: Query execution was interrupted (max_statement_time exceeded)
       
      The result from queries just before the failure was:
      < snip >
      DROP TABLE t1;
      #
      # MDEV-7011:MAX_STATEMENT_TIME has no effect in a procedure after
      # a previous successful statement
      #
      create table t1 (i int);
      insert into t1 values (1),(2),(3),(4);
      insert into t1 select a.* from t1 a, t1 b, t1 c, t1 d, t1 e, t1 f, t1 g;
      create procedure pr()
      begin
      select 1;
      select sql_no_cache * from t1 where i > 5;
      select sql_no_cache * from t1 where i > 5;
      end |
      set max_statement_time = 0.001;
      call pr();
      1
      1
      ERROR 70100: Query execution was interrupted (max_statement_time exceeded)
      drop procedure pr;

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                serg Sergei Golubchik
                Reporter:
                elenst Elena Stepanova
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: