Do not manually include fast_run in test_shape_i_*

It doesn't make sense to include `fast_run` if `fast_compile` mode is being used. Some rewrites such as the FusionOptimizer are not compatible with `fast_compile` mode which prevents the creation of C thunks. The FusionOptimizer has no way of knowing this is the case, and assumes it is safe to return Composites with more than 32 operands, even though that's not the case with the Python perform method.

Author: ricardoV94

tests/tensor/test_subtensor.py

@@ -986,7 +986,7 @@ def test_adv_sub1_idx_broadcast(self):
     def test_shape_i_const(self):
         # Each axis is treated independently by shape_i/shape operators
 
-        mode_opt = self.mode.including("fast_run")
+        mode_opt = self.mode
         data = self.shared(np.array(np.arange(5), dtype=self.dtype))
         for start in [None] + [-8, -5, -1, 0, 1, 5, 8]:
             outs = []
@@ -1004,7 +1004,7 @@ def test_shape_i_const(self):
     def test_shape_i_scalar(self):
         # Each axis is treated independently by shape_i/shape operators
 
-        mode_opt = self.mode.including("fast_run")
+        mode_opt = self.mode
 
         v_data = np.array(np.arange(5), dtype=self.dtype)
         t_data = self.shared(v_data)