Disabling rpl_heartbeat_timestamp in valgrind and parallel mode

Summary: This is a time dependent testcase so it doesn't work well with these options Squash with: D5006919 Test Plan: MTR Reviewers: mung Reviewed By: mung Subscribers: [email protected] Differential Revision: https://phabricator.intern.facebook.com/D5131105 Tasks: 18642506 Signature: t1:5131105:1495738174:749a7ca2f3ad1628ace693d306252e4c0ce6b68a
facebook · May 25, 2017 · d39c930 · d39c930
1 parent 6258aff
commit d39c930
Showing 1 changed file with 3 additions and 0 deletions.
diff --git a/mysql-test/suite/rpl/t/rpl_heartbeat_timestamp.test b/mysql-test/suite/rpl/t/rpl_heartbeat_timestamp.test
@@ -7,6 +7,9 @@
 # slave_2 is between 0 and heartbeat period. We then kill the master and
 # check if the lag on slave_2 keeps increasing.
 
+source include/not_valgrind.inc;
+source include/not_parallel.inc;
+
 let $rpl_server_count= 3;
 let $rpl_topology= 1->2->3;
 source include/rpl_init.inc;