An error occurred fetching the project authors.
  1. 20 Jan, 2010 1 commit
  2. 07 Jan, 2010 1 commit
  3. 06 Jan, 2010 3 commits
  4. 16 Dec, 2009 1 commit
  5. 26 Nov, 2009 1 commit
  6. 21 Nov, 2009 1 commit
  7. 11 Nov, 2009 1 commit
  8. 03 Nov, 2009 1 commit
    • Vladislav Vaintroub's avatar
      Bug #47423 mtr connects to wrong database · 2377eed3
      Vladislav Vaintroub authored
      The reason for the bug is that mysqtest as well as other client tools
      running in test suite (mysqlbinlog, mysqldump) will first try to connect 
      whatever database has created shared memory with default base name 
      "MySQL" and use this. (Same effect could be seen on Unix if mtr would
      not care to calculate "port" and "socket" parameter).
            
      The fix ensures that all client tools and  running in mtr use unique  
      per-database shared memory base parameters, so there is no possibility
      to clash with already installed one. We use socket name for shared memory 
      base (it's known to be unique). This shared-memory-base is written to the
      MTR config file to the [client] and [mysqld] sections. Fix made also made 
      sure all client tools understand and correctly handle --shared-memory-base.
      Prior to this patch  it was not the case for  mysqltest, mysqlbinlog and 
      mysql_client_test.
            
      All new connections done from mtr scripts via connect() will by default 
      set shared-memory-base. And finally, there is a possibility to force 
      shared memory or pipe connection and overwrite shared memory/pipe base name
      from within mtr scripts via optional PIPE or SHM modifier. This functionality
      was manually backported from 6.0
      (original patch  http://lists.mysql.com/commits/74749)
      2377eed3
  9. 08 Oct, 2009 1 commit
  10. 10 Sep, 2009 1 commit
  11. 02 Sep, 2009 1 commit
  12. 19 Aug, 2009 1 commit
  13. 18 Aug, 2009 1 commit
  14. 11 Aug, 2009 1 commit
  15. 27 May, 2009 1 commit
  16. 26 May, 2009 1 commit
  17. 25 May, 2009 1 commit
  18. 07 May, 2009 1 commit
  19. 28 Apr, 2009 1 commit
  20. 13 Mar, 2009 1 commit
  21. 11 Mar, 2009 1 commit
  22. 13 Feb, 2009 1 commit
    • Rafal Somla's avatar
      Modifications to MTR and mysqltest to improve feedback from the latter when · bdbe393d
      Rafal Somla authored
      testcase checks are made.
            
      MTR spawns mysqltest to run check-testcase test before and after each testcase 
      it runs. It can also run check-warnings using mysqltest. Since it happened on PB 
      that these checks hanged, this patch provides additional feedback to help 
      investigating such failures:
            
      - mysqltest is modified to give feedback about main steps in execution of a 
      testcase if run in verbose mode (including connection to the server),
           
      - MTR is modified to run mysqltest in verbose mode when doing check-testcase or 
      check-warnings. The diagnostic output from mysqltest is preserved so that it is 
      saved upon test failure.
      
      client/mysqltest.cc:
        Add verbose messages informing about main steps in execution of a testcase.
      mysql-test/mysql-test-run.pl:
        - When doing check-testcase or check-warnings run mysqltest in verbose mode.
        - Do not delete the mysqltest's error log if errors are detected during these
      bdbe393d
  23. 21 Jan, 2009 1 commit
    • Bjorn Munch's avatar
      Bug #40399 Please make mtr print stack trace after every failure · 089663f9
      Bjorn Munch authored
      SIGABRT is sent to relevant processes after a timeout
      
      
      client/mysqltest.cc:
        Fixed signal handlers to mysqltest actually dumps core
      mysql-test/lib/My/CoreDump.pm:
        Added support for dbx
      mysql-test/lib/My/SafeProcess.pm:
        Added dump_core to force process to dump core
      mysql-test/lib/My/SafeProcess/safe_process.cc:
        Traps SIGABRT and sends this on to child
      mysql-test/mysql-test-run.pl:
        When test times out, force core dumps on mysqltest and servers
      089663f9
  24. 15 Jan, 2009 1 commit
  25. 25 Dec, 2008 1 commit
    • He Zhenxing's avatar
      BUG#40704 main.events_restart fails sporadically in pushbuild: "server has gone away" · 2070da70
      He Zhenxing authored
      mysqltest command 'shutdown_server' is supposed to shutdown the server
      and wait for it to be gone, and kill it when timeout. But because the
      arguments passed to my_kill were in the wrong order, 'shutdown_server'
      does not wait nor kill the server at all. So after 'shutdown_server',
      the server is still running, and the server may still accepting
      connections.
      
      
      mysql-test/include/mtr_warnings.sql:
        Suppress forcing close thread messages when server shuts down
      mysql-test/include/restart_mysqld.inc:
        wait_until_disconnected.inc is not required after fix shutdown_server command
      2070da70
  26. 14 Nov, 2008 3 commits
  27. 10 Nov, 2008 1 commit
  28. 23 Oct, 2008 1 commit
    • Sven Sandberg's avatar
      BUG#35701: please allow test language variables in connection and sync_slave_with_master · c7f8ffe7
      Sven Sandberg authored
      Problem: In the mysqltest language, it was not possible to set the current
      connection from a variable, and it was not possible to read the current
      connection.
      Fix: Allow setting the connection from a variable, like:
      connection $variable;
      and introduce the mysqltest language variable $CURRENT_CONNECTION, which
      holds the name of the current connection.
      
      
      client/mysqltest.cc:
        - Made select_connection use the common argument parser instead of its own
        home-rolled version. That allows variable expansion, for instance.
        - Made select_connection_name set the variable $CURRENT_CONNECTION, so that
        test scripts can use that.
        - Refactored a bit so that stuff that needs to be done when changing connection
        is located to one place.
      mysql-test/t/mysqltest.test:
        Added test case for $CURRENT_CONNECTION and "connection $variable"
      c7f8ffe7
  29. 29 Aug, 2008 1 commit
  30. 25 Aug, 2008 1 commit
  31. 09 Aug, 2008 4 commits
  32. 04 Aug, 2008 2 commits