main.percona_query_response_time failure in Jenkins

Bug #803867 reported by Alexey Kopytov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Fix Released
Undecided
Oleg Tsarev
5.1
Fix Released
Undecided
Oleg Tsarev
5.5
Fix Released
Undecided
Oleg Tsarev

Bug Description

http://jenkins.percona.com/view/Percona%20Server%205.1/job/percona-server-5.1-trunk/BUILD_TYPE=debug-no-Werror,Host=ubuntu-natty-64bit/30/console

main.percona_query_response_time w8 [ fail ]
        Test ended at 2011-06-28 15:43:28

CURRENT_TEST: main.percona_query_response_time
--- /mnt/workspace/percona-server-5.1-trunk/BUILD_TYPE/debug-no-Werror/Host/ubuntu-natty-64bit/Percona-Server-5.1.57-rel12.8/mysql-test/r/percona_query_response_time.result 2011-06-28 18:30:14.000000000 +0300
+++ /mnt/workspace/percona-server-5.1-trunk/BUILD_TYPE/debug-no-Werror/Host/ubuntu-natty-64bit/Percona-Server-5.1.57-rel12.8/mysql-test/r/percona_query_response_time.reject 2011-06-28 18:43:27.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
+9 19 16 4 44
+2 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-server:
status: New → Confirmed
Oleg Tsarev (tsarev)
Changed in percona-server:
assignee: nobody → Oleg Tsarev (tsarev)
Oleg Tsarev (tsarev)
Changed in percona-server:
status: Confirmed → Fix Committed
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-2659

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.