**Reported in Launchpad by Laurynas Biveinis last update 11-02-2013 08:11:37

1) 5.1 test percona_log_slow_timestamp_every.test / 5.5 test percona_slow_query_log_timestamp_always.test has a part

SET GLOBAL slow_query_log_timestamp_always=OFF;
SELECT 1;
SELECT 1;
SELECT 1;

which is meant to test that consecutive slow query log that have the same time are not timestamped. Of course, this does not work as intended on loaded test hosts as nothing prevents these queries from getting differing timestamps. This is supported by Jenkins:
http://jenkins.percona.com/job/percona-server-5.1-trunk/641/BUILD_TYPE=debug,Host=ubuntu-precise-64bit/testReport/junit/%28root%29/main/percona_log_slow_timestamp_every/
http://jenkins.percona.com/job/percona-server-5.1-trunk/641/BUILD_TYPE=debug,Host=ubuntu-precise-64bit/testReport/junit/%28root%29/main/percona_log_slow_timestamp_every_2/
http://jenkins.percona.com/job/percona-server-5.5-trunk/187/BUILD_TYPE=debug,Host=centos5-32/testReport/junit/%28root%29/main/percona_slow_query_log_timestamp_always/

2) Test percona_slow_query_log_timestamp_always-cl.test
SHOW VARIABLES LIKE 'slow_query_log_timestamp_always';
SHOW GLOBAL VARIABLES LIKE 'slow_query_log_timestamp_always';
with -master.opt: --slow_query_log_timestamp_always should probably belong to the sys_vars suite.