Test percona_slow_query_log_timestamp_always is unstable

Bug #1615945 reported by Laurynas Biveinis
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Status tracked in 5.7
5.5
In Progress
Low
Unassigned
5.6
In Progress
Low
Unassigned
5.7
Invalid
Low
Unassigned

Bug Description

On 5.5 trunk:

main.percona_slow_query_log_timestamp_always w3 [ fail ]
        Test ended at 2016-08-22 14:32:11

CURRENT_TEST: main.percona_slow_query_log_timestamp_always
--- /mnt/workspace/percona-server-5.5-trunk/BUILD_TYPE/release/Host/ubuntu-wily-64bit/mysql-test/r/percona_slow_query_log_timestamp_always.result 2016-08-22 21:07:58.582395832 +0300
+++ /mnt/workspace/percona-server-5.5-trunk/BUILD_TYPE/release/Host/ubuntu-wily-64bit/mysql-test/r/percona_slow_query_log_timestamp_always.reject 2016-08-22 21:32:11.475930027 +0300
@@ -10,7 +10,7 @@
 2
 [log_stop.inc] percona_slow_extended_query_log_1
 [log_grep.inc] file: percona_slow_extended_query_log_1 pattern: ^# Time: \d{6} (\d| )\d:\d\d:\d\d$
-[log_grep.inc] lines: 3
+[log_grep.inc] lines: 0
 SET GLOBAL slow_query_log_timestamp_always=default;
 SET SESSION long_query_time=default;
 SET SESSION min_examined_row_limit=default;

mysqltest: Result content mismatch

tags: added: ci
tags: added: slow-extended
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

Failure with actual slow log contents

main.percona_slow_query_log_timestamp_always w1 [ fail ]
        Test ended at 2016-08-25 08:59:39

CURRENT_TEST: main.percona_slow_query_log_timestamp_always
--- /mnt/workspace/percona-server-5.5-asan-param/BUILD_TYPE/release-asan/Host/ubuntu-xenial-64bit/mysql-test/r/percona_slow_query_log_timestamp_always.result 2016-08-25 15:40:36.550089324 +0300
+++ /mnt/workspace/percona-server-5.5-asan-param/BUILD_TYPE/release-asan/Host/ubuntu-xenial-64bit/mysql-test/r/percona_slow_query_log_timestamp_always.reject 2016-08-25 15:59:39.673990416 +0300
@@ -10,7 +10,19 @@
 2
 [log_stop.inc] percona_slow_query_log_timestamp_always
 [log_grep.inc] file: percona_slow_query_log_timestamp_always pattern: ^# Time: \d{6} (\d| )\d:\d\d:\d\d$ expected_matches: 3
-[log_grep.inc] found expected match count: 3
+[log_grep.inc] ERROR: expected matches: 3, actual matches: 1
+[log_grep.inc] log file at /mnt/workspace/percona-server-5.5-asan-param/BUILD_TYPE/release-asan/Host/ubuntu-xenial-64bit/mysql-test/var/1/percona_slow_query_log_timestamp_always.slog
+/mnt/workspace/percona-server-5.5-asan-param/BUILD_TYPE/release-asan/Host/ubuntu-xenial-64bit/sql/mysqld, Version: 5.5.51-38.1-log (MySQL Community Server (GPL)). started with:
+Tcp port: 13001 Unix socket: /tmp/letsTt0Yn2/1/mysqld.1.sock
+Time Id Command Argument
+# Time: 160825 15:59:39
+# User@Host: root[root] @ localhost []
+# Thread_id: 49 Schema: test Last_errno: 0 Killed: 0
+# Query_time: 0.000241 Lock_time: 0.000000 Rows_sent: 1 Rows_examined: 0 Rows_affected: 0 Rows_read: 0
+# Bytes_sent: 56
+use test;
+SET timestamp=1472129979;
+SELECT 2;
 SET GLOBAL slow_query_log_timestamp_always=default;
 SET SESSION long_query_time=default;
 SET SESSION min_examined_row_limit=default;

mysqltest: Result content mismatch

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-2176

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.