An error occurred fetching the project authors.
  1. 30 Dec, 2010 1 commit
  2. 20 Dec, 2010 1 commit
  3. 24 Nov, 2010 2 commits
  4. 07 Nov, 2010 1 commit
  5. 01 Nov, 2010 1 commit
  6. 27 Oct, 2010 1 commit
  7. 07 Oct, 2010 1 commit
  8. 06 Oct, 2010 1 commit
  9. 24 Sep, 2010 1 commit
  10. 07 Sep, 2010 1 commit
  11. 31 Aug, 2010 1 commit
  12. 17 Aug, 2010 1 commit
  13. 03 Aug, 2010 1 commit
    • Georgi Kodinov's avatar
      Bug #42144: plugin_load fails · 534e6933
      Georgi Kodinov authored
      The enum system variables were handled inconsistently 
      as ints, unsigned int and unsigned long on various places.
      This caused problems on platforms on which 
      sizeof(int) != sizeof(long).
      Fixed by homogenizing the type of the enum variables
      to unsigned int, since it's size compatible with the C enum
      type. 
      Removed the test from the experimental list.
      534e6933
  14. 26 Jul, 2010 1 commit
  15. 28 Jun, 2010 1 commit
  16. 26 Jun, 2010 1 commit
  17. 15 Jun, 2010 1 commit
  18. 03 Jun, 2010 1 commit
  19. 01 Jun, 2010 2 commits
  20. 03 Jun, 2010 1 commit
  21. 11 May, 2010 1 commit
  22. 04 May, 2010 1 commit
  23. 30 Apr, 2010 1 commit
    • Alexander Nozdrin's avatar
      Patch for Bug#52356: query_cache_debug fails on Linux. · c784ee27
      Alexander Nozdrin authored
      There were two problems here:
        1. misleading error message
        2. abusing KILL QUERY in the test case
      
      1. The server reported "'DELETE FROM t1' failed: 1689: Wait on a lock was
      aborted due to a pending exclusive lock", while the proper error message
      should be "'DELETE FROM t1' failed: 1317: Query execution was interrupted".
      
      The problem is that the server has two different flags for
      signalling that a query is being killed: THD::killed and
      mysys_var::abort. The test case triggers a race: sometimes
      mysys_var::abort is set earlier than THD::killed. That leads
      to the following situation:
      
        - thr_lock() checks mysys_var::abort and returns error status,
          since mysys_var::abort is set;
      
        - the caller (mysql_lock_tables()) gets an error from thr_lock(),
          but THD::killed is not set, so it decides that thr_lock() couldn't
          get a lock due to a pending exclusive lock.
      
      This is a known issue with the server and it's not going to be fixed soon.
      
      5.5 differs from 5.1 here as follows: when thr_lock() returns an error:
        - 5.1 continues trying thr_lock() until success;
        - 5.5 propagates the error
      
      2. The test case uses KILL QUERY is a highly concurent environment.
      
      The fix is to wait for the dying statement to rest in peace before
      executing another DELETE FROM t1.
      c784ee27
  24. 26 Apr, 2010 1 commit
  25. 10 Apr, 2010 1 commit
  26. 23 Mar, 2010 1 commit
  27. 22 Mar, 2010 1 commit
  28. 05 Mar, 2010 1 commit
  29. 02 Mar, 2010 1 commit
  30. 22 Feb, 2010 1 commit
  31. 17 Feb, 2010 1 commit
  32. 01 Feb, 2010 1 commit
  33. 31 Jan, 2010 1 commit
  34. 28 Jan, 2010 1 commit
    • Alexander Nozdrin's avatar
      Make the following tests experimental: · 5594d64c
      Alexander Nozdrin authored
        - main.outfile_loaddata @solaris due to Bug#46895
        - main.signal_demo3 @solaris due to Bug#47791
        - main.sp @solaris due to Bug#47791
        - rpl.rpl_slave_load_remove_tmpfile @windows due to Bug#50474
      5594d64c
  35. 27 Jan, 2010 1 commit
    • 's avatar
      Bug #49191 rpl_get_master_version_and_clock failed on PB2: COM_REGISTER_SLAVE failed · 73cfad9f
      authored
      The 'rpl_get_master_version_and_clock' test verifies if the slave I/O
      thread tries to reconnect to master when it tries to get the values of
      the UNIX_TIMESTAMP, SERVER_ID from master under network disconnection.
      So the master server is restarted for making the transient network
      disconnection, during the period the COM_REGISTER_SLAVE failures are
      produced in server log file when the slave I/O thread tries to
      register on master.
      
      To fix the problem, suppress COM_REGISTER_SLAVE failures in server log
      file by mtr suppression, because they are expected.
      73cfad9f
  36. 26 Jan, 2010 1 commit
  37. 25 Jan, 2010 1 commit
  38. 23 Jan, 2010 1 commit