main.percona_log_slow_sp_statements and other slow query log tests fail sporadically

Bug #1163680 reported by Alexey Kopytov on 2013-04-03
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Percona Server
Medium
Yura Sorokin
5.1
Medium
Yura Sorokin
5.5
Medium
Yura Sorokin
5.6
Medium
Yura Sorokin

Bug Description

main.percona_log_slow_sp_statements fails sporadically in Jenkins as follows:

_StringException: Text attachment: traceback
------------
Comment:

Logfile:
CURRENT_TEST: main.percona_log_slow_sp_statements
--- /mnt/workspace/percona-server-5.5-param/BUILD_TYPE/debug/Host/centos6-64/Percona-Server/mysql-test/r/percona_log_slow_sp_statements.result 2013-03-06 21:36:23.000000000 +0300
+++ /mnt/workspace/percona-server-5.5-param/BUILD_TYPE/debug/Host/centos6-64/Percona-Server/mysql-test/r/percona_log_slow_sp_statements.reject 2013-04-02 22:24:02.000000000 +0300
@@ -13,7 +13,7 @@
 1
 [log_stop.inc] percona.slow_extended.sp1
 [log_grep.inc] file: percona.slow_extended.sp1 pattern: SELECT 1;
-[log_grep.inc] lines: 1
+[log_grep.inc] lines: 0
 SET GLOBAL log_slow_sp_statements=OFF;
 [log_start.inc] percona.slow_extended.sp2
 CALL test_f();

mysqltest: Result content mismatch
------------

tags: added: ci

I do not see failures for this test in Jenkins for 5.6 since April 3.

The test is not merged there yet. Any fixes it will need on the lower versions will almost certainly have to be upmerged to 5.6 too.

See also bug 1098857.

summary: - main.percona_log_slow_sp_statements fails sporadically
+ main.percona_log_slow_sp_statements and other slow query log tests fail
+ sporadically
tags: added: slow-extended
Yura Sorokin (yura-sorokin) wrote :

The bug can no longer be reproduced on neither 5.1, nor 5.5, nor 5.6.

The following scripts were used

1. All "percona_log_slow_*" test run in parallel
*******************************************************
run_mixed.sh
*******************************************************
./mtr \
 --parallel=16 \
 --repeat=16 \
 percona_log_slow_admin_statements-config_false \
 percona_log_slow_admin_statements-config_foo \
 percona_log_slow_admin_statements-config \
 percona_log_slow_admin_statements-config_true \
 percona_log_slow_admin_statements \
 percona_log_slow_filter-cl \
 percona_log_slow_global_control_default \
 percona_log_slow_innodb \
 percona_log_slow_query_plan_qc \
 percona_log_slow_query_plan \
 percona_log_slow_slave_statements-cl \
 percona_log_slow_slave_statements-innodb \
 percona_log_slow_slave_statements \
 percona_log_slow_sp_statements-cl \
 percona_log_slow_sp_statements \
 percona_log_slow_verbosity-cl \
 percona_log_slow_verbosity
*****************************************************

2. The same test "percona_log_slow_sp_statements" run in parallel
*******************************************************
run_single.sh
*******************************************************
./mtr \
 --parallel=16 \
 --repeat=128 \
 percona_log_slow_sp_statements \
 percona_log_slow_sp_statements \
 percona_log_slow_sp_statements \
 percona_log_slow_sp_statements \
 percona_log_slow_sp_statements \
 percona_log_slow_sp_statements \
 percona_log_slow_sp_statements \
 percona_log_slow_sp_statements \
 percona_log_slow_sp_statements \
 percona_log_slow_sp_statements \
 percona_log_slow_sp_statements \
 percona_log_slow_sp_statements \
 percona_log_slow_sp_statements \
 percona_log_slow_sp_statements \
 percona_log_slow_sp_statements \
 percona_log_slow_sp_statements
*******************************************************

These scripts were also run on 5.1, 5.5 and 5.6 with "./mtr --debug" option enabled in order to slow down code execution and provoke different set of race conditions.

For 5.5 and 5.6 "run_single.sh" were also run with original "percona_log_slow_sp_statements .test" (an older version of this file corresponding to the code when the bug was submitted).

Yura Sorokin (yura-sorokin) wrote :

No signs of this test failure on both 5.5 and 5.6 in Jenkins for at least 1 months (as of September 21, 2015).
Setting status to "Incomplete".

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers