main.percona_query_response_time fails on 5.1.52-rel12.3

Bug #684215 reported by Aleksandr Kuzminsky
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Fix Released
High
Oleg Tsarev

Bug Description

main.percona_query_response_time [ fail ]
        Test ended at 2010-12-01 13:09:40

CURRENT_TEST: main.percona_query_response_time
--- /home/buildbot/slaves/percona-server-51-12/DEB_Debian_etch_amd64/work/percona-server-5.1.52-12.3-153.etch/mysql-test/r/percona_query_response_time.result 2010-12-01 19:44:31.000000000 +0300
+++ /home/buildbot/slaves/percona-server-51-12/DEB_Debian_etch_amd64/work/percona-server-5.1.52-12.3-153.etch/mysql-test/r/percona_query_response_time.reject 2010-12-01 21:09:39.000000000 +0300
@@ -131,11 +131,14 @@
 (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
-1 20 15 5 44
-10 20 15 5 44
-1 20 15 5 44
-5 20 15 5 44
-3 20 15 5 44
+14 58 15 8 44
+6 58 15 8 44
+10 58 15 8 44
+9 58 15 8 44
+10 58 15 8 44
+1 58 15 8 44
+5 58 15 8 44
+3 58 15 8 44
 SELECT COUNT(*) as region_count FROM INFORMATION_SCHEMA.QUERY_RESPONSE_TIME;
 region_count
 44
@@ -259,9 +262,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
-1 20 17 3 14
-11 20 17 3 14
-8 20 17 3 14
+20 58 17 4 14
+19 58 17 4 14
+11 58 17 4 14
+8 58 17 4 14
 SELECT COUNT(*) as region_count FROM INFORMATION_SCHEMA.QUERY_RESPONSE_TIME;
 region_count
 14
@@ -355,9 +359,11 @@
 (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
-1 20 17 3 17
-11 20 17 3 17
-8 20 17 3 17
+16 58 17 5 17
+21 58 17 5 17
+2 58 17 5 17
+11 58 17 5 17
+8 58 17 5 17
 SELECT COUNT(*) as region_count FROM INFORMATION_SCHEMA.QUERY_RESPONSE_TIME;
 region_count
 17
@@ -454,9 +460,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
-1 20 17 3 7
-11 20 17 3 7
-8 20 17 3 7
+19 58 17 4 7
+20 58 17 4 7
+11 58 17 4 7
+8 58 17 4 7
 SELECT COUNT(*) as region_count FROM INFORMATION_SCHEMA.QUERY_RESPONSE_TIME;
 region_count
 7
@@ -543,9 +550,9 @@
 (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
-1 20 17 3 6
-11 20 17 3 6
-8 20 17 3 6
+38 58 17 3 6
+12 58 17 3 6
+8 58 17 3 6
 SELECT COUNT(*) as region_count FROM INFORMATION_SCHEMA.QUERY_RESPONSE_TIME;
 region_count
 6

mysqltest: Result content mismatch

Related branches

Changed in percona-server:
milestone: none → 5.1.52-12.3
summary: - main.percona_query_response_time-stored fails on 5.1.52-rel12.3
+ main.percona_query_response_time fails on 5.1.52-rel12.3
Changed in percona-server:
assignee: nobody → Oleg Tsarev (tsarev)
Changed in percona-server:
importance: Undecided → High
Oleg Tsarev (tsarev)
Changed in percona-server:
status: New → Fix Committed
Changed in percona-server:
status: Fix Committed → Fix Released
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-447

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.