remove task tracker test from follower schedule

src/test/regress/expected/multi_follower_task_tracker.out

@@ -1,27 +0,0 @@
-\c - - - :master_port
--- do some setup
-CREATE TABLE tab(a int, b int);
-SELECT create_distributed_table('tab', 'a');
- create_distributed_table
----------------------------------------------------------------------
-
-(1 row)
-
-INSERT INTO tab (a, b) VALUES (1, 1);
-INSERT INTO tab (a, b) VALUES (1, 2);
-\c - - - :follower_master_port
-RESET citus.task_executor_type;
-SELECT * FROM tab;
- a | b
----------------------------------------------------------------------
- 1 | 1
- 1 | 2
-(2 rows)
-
-SET citus.task_executor_type TO 'task-tracker';
-SELECT * FROM tab;
-ERROR:  task tracker queries are not allowed while citus.use_secondary_nodes is 'always'
-HINT:  try setting citus.task_executor_type TO 'adaptive'
--- clean up
-\c - - - :master_port
-DROP TABLE tab;

src/test/regress/multi_follower_schedule

@@ -2,7 +2,6 @@ test: multi_follower_sanity_check
 test: multi_follower_select_statements
 test: multi_follower_dml
 test: multi_follower_configure_followers
-test: multi_follower_task_tracker
 
 # test that no tests leaked intermediate results. This should always be last
 test: ensure_no_intermediate_data_leak

src/test/regress/sql/multi_follower_task_tracker.sql

@@ -1,22 +0,0 @@
-\c - - - :master_port
-
--- do some setup
-
-CREATE TABLE tab(a int, b int);
-SELECT create_distributed_table('tab', 'a');
-
-INSERT INTO tab (a, b) VALUES (1, 1);
-INSERT INTO tab (a, b) VALUES (1, 2);
-
-\c - - - :follower_master_port
-
-RESET citus.task_executor_type;
-SELECT * FROM tab;
-SET citus.task_executor_type TO 'task-tracker';
-SELECT * FROM tab;
-
--- clean up
-
-\c - - - :master_port
-
-DROP TABLE tab;