1. 04 Apr, 2016 1 commit
  2. 24 Mar, 2016 1 commit
  3. 21 Mar, 2016 11 commits
  4. 18 Mar, 2016 1 commit
  5. 17 Mar, 2016 3 commits
  6. 16 Mar, 2016 1 commit
  7. 15 Mar, 2016 1 commit
  8. 12 Mar, 2016 1 commit
    • Elena Stepanova's avatar
      MDEV-9713 Sporadic test failure: sys_vars.innodb_buffer_pool_load_now_basic · 0125e588
      Elena Stepanova authored
      It could have happened that one of previous tests already executed
      buffer pool dump and set the status variable value, so when it's been
      checked, the check passes too early, before the dump starts and
      the dump file is created. See more detailed explanation in MDEV-9713.
      
      Fixed by waiting for the current time to change in case it equals
      to the timestamp in the status variable, and then checking that
      the status variable not only matches the expected pattern, but also
      differs from the previous value, whatever it was.
      0125e588
  9. 11 Mar, 2016 1 commit
  10. 10 Mar, 2016 1 commit
    • Sergey Vojtovich's avatar
      Fixed false errors returned by logrotate script · 8942824a
      Sergey Vojtovich authored
      Logrotate script assumed an error if mysqladmin failed to connect to server
      and there's mysqld process exists. However there can be non-system instance of
      mysqld running (e.g. in docker) making this assumption wrong.
      
      Check pid file existance instead.
      8942824a
  11. 09 Mar, 2016 1 commit
  12. 08 Mar, 2016 1 commit
  13. 07 Mar, 2016 1 commit
  14. 04 Mar, 2016 1 commit
  15. 03 Mar, 2016 1 commit
    • Kristian Nielsen's avatar
      MDEV-9595: Shutdown takes forever with many replication channels · f8251911
      Kristian Nielsen authored
      There was a race between end_slave() and cleanup code at the end of
      handle_slave_sql(). This could cause access to master_info_index and
      global_rpl_thread_pool after they had been freed.
      
      Fix by skipping that cleanup if server shutdown is in progress, as is done
      in other parts of the code as well (the cleanup, which stops worker threads
      that are not needed anymore, is redundant anyway when the server is shutting
      down).
      f8251911
  16. 01 Mar, 2016 1 commit
  17. 29 Feb, 2016 1 commit
  18. 26 Feb, 2016 1 commit
    • Elena Stepanova's avatar
      MDEV-4070 sys_vars.secure_file_priv fails sporadically if it's executed with --mem · c29e450e
      Elena Stepanova authored
      The test created a file in location relative to the datadir
      (a few levels above datadir).
      The file was created by MariaDB server (via INTO OUTFILE), and
      later removed by mysqltest (via remove_file). The problem is that
      when the vardir is a symlink, MariaDB server and mysqltest can
      resolve such paths differently. MariaDB server would return back
      to where the symlink is located, while mysqltest would go above
      the real directory. For example, if the test is run with --mem,
      and /bld/5.5/mysql-test/var points at /dev/shm/var_auto_X, then
      SELECT INTO OUTFILE created a file in /bld/5.5/mysql-test , but
      remove_file would look for it in /dev/shm/.
      
      The test is re-written so that all paths are resolved in perl,
      the logic itself hasn't changed.
      c29e450e
  19. 25 Feb, 2016 1 commit
  20. 18 Feb, 2016 1 commit
  21. 17 Feb, 2016 8 commits