main.percona_query_response_time fails

Bug #746517 reported by Alexey Kopytov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
percona-projects-qa
Fix Released
Undecided
Alexey Kopytov

Bug Description

I get the following failure in 5.5.10:

 main.percona_query_response_time [ fail ]
        Test ended at 2011-03-31 19:39:35

CURRENT_TEST: main.percona_query_response_time
--- /Users/kaa/src/percona/5.5/Percona-Server/mysql-test/r/percona_query_response_time.result 2011-03-31 16:17:49.000000000 +0300
+++ /Users/kaa/src/percona/5.5/Percona-Server/mysql-test/r/percona_query_response_time.reject 2011-03-31 18:39:34.000000000 +0300
@@ -132,10 +132,10 @@
 (SELECT COUNT(*) FROM INFORMATION_SCHEMA.QUERY_RESPONSE_TIME) as region_count
 FROM INFORMATION_SCHEMA.QUERY_RESPONSE_TIME as d WHERE d.count > 0;
 count query_count query_total not_zero_region_count region_count
-10 19 15 4 44
-1 19 15 4 44
-5 19 15 4 44
-3 19 15 4 44
+10 19 16 4 44
+1 19 16 4 44
+5 19 16 4 44
+3 19 16 4 44
 SELECT COUNT(*) as region_count FROM INFORMATION_SCHEMA.QUERY_RESPONSE_TIME;
 region_count
 44

mysqltest: Result content mismatch

Related branches

Changed in percona-projects-qa:
assignee: nobody → Alexey Kopytov (akopytov)
status: New → Fix Committed
Changed in percona-projects-qa:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.