| Bug #28830 | Test case log_state fails on VMWare Windows clone due to loaded system | ||
|---|---|---|---|
| Submitted: | 1 Jun 2007 10:26 | Modified: | 9 Aug 2007 13:27 |
| Reporter: | Mats Kindahl | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Tests | Severity: | S3 (Non-critical) |
| Version: | OS: | Any | |
| Assigned to: | Konstantin Osipov | CPU Architecture: | Any |
[8 Aug 2007 11:49]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/32246 ChangeSet@1.2562, 2007-08-08 15:49:19+04:00, kostja@bodhi.(none) +2 -0 A fix for Bug#28830 Test case log_state fails on VMWare Windows clone due to loaded system
[8 Aug 2007 11:52]
Konstantin Osipov
Queued in 5.1-runtime
[9 Aug 2007 13:18]
Bugs System
Pushed into 5.1.22-beta
[9 Aug 2007 13:27]
Konstantin Osipov
Test case failure.
Description: When executing log_state on a heavily loaded system, the select statement that is issued to investigate what is in the slow log itself goes into the slow log. How to repeat: Run test log_state on a system where the response-time is long, e.g., on a heavily loaded system Here is the output from pushbuild. *** r/log_state.result Fri Jun 1 10:07:33 2007 --- r/log_state.reject Fri Jun 1 10:23:06 2007 *************** *** 46,51 **** --- 46,52 ---- 0 select * from mysql.slow_log; start_time user_host query_time lock_time rows_sent rows_examined db last_insert_id insert_id server_id sql_text + TIMESTAMP USER_HOST QUERY_TIME 00:00:01 0 0 test 0 0 1 select * from mysql.slow_log TIMESTAMP USER_HOST QUERY_TIME 00:00:00 1 0 test 0 0 1 select sleep(2) show global variables where Variable_name = 'log' or Variable_name = 'log_slow_queries' or Suggested fix: Add the following WHERE clause to the select sql_text NOT LIKE 'select%mysql.slow_log%'