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

main.func_isnull fails in buildbot on Windows 32bit

    XMLWordPrintable

Details

    Description

      http://buildbot.askmonty.org/buildbot/builders/win32-debug2/builds/6560/steps/test/logs/stdio

      main.func_isnull                         [ fail ]
              Test ended at 2014-11-21 17:41:53
       
      CURRENT_TEST: main.func_isnull
      mysqltest: At line 24: query 'SELECT ISNULL((SELECT GET_LOCK('Bug#53933', 0) FROM t1 GROUP BY f1)) AS f2
      FROM t1 GROUP BY f1 HAVING f2 = f2' failed: 2013: Lost connection to MySQL server during query
       
      The result from queries just before the failure was:
      drop table if exists t1;
      create table t1 (id int auto_increment primary key not null, mydate date not null);
      insert into t1 values (0,"2002-05-01"),(0,"2002-05-01"),(0,"2002-05-01");
      flush tables;
      select * from t1 where isnull(to_days(mydate));
      id	mydate
      drop table t1;
      #
      # Bug#53933 crash when using uncacheable subquery in the having clause of outer query
      #
      CREATE TABLE t1 (f1 INT);
      INSERT INTO t1 VALUES (0),(0);
      SELECT ISNULL((SELECT GET_LOCK('Bug#53933', 0) FROM t1 GROUP BY f1)) AS f2
      FROM t1 GROUP BY f1 HAVING f2 = f2;
       
       
      Server [mysqld.1 - pid: 270144, winpid: 270144, exit: 768] failed during test run
      Server log from this test:
      ----------SERVER LOG START-----------
      ----------SERVER LOG END-------------

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              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.