Remove hardcoded data shape assertion in small pipeline test

The shape of the data being transferred is in principle dependent on the
max slices calculation, which in turn is dependent on the GPU model
being used. As the GPU model can vary widely, the max slices and
therefore the data shape can vary widely, making this assertion
difficult to pass if run on different GPUs.

As the purpose of the small pipeline tests is not focused on specific
data shapes, but functional behaviour of pipeline execution, asserting
that there's a line in the logfile corresponding to a data transfer
occurring for GPU 0 is sufficient, and there's no need to be specific
about the shape of the data that was transferred.

Author: yousefmoazzam

tests/test_pipeline_small.py

@@ -163,9 +163,7 @@ def test_run_pipeline_FBP3d_tomobar_denoising(
     assert "Preview: (0:180, 0:128, 0:160)" in verbose_log_contents
     assert "Data shape is (180, 128, 160) of type uint16" in verbose_log_contents
     assert "The amount of the available GPU memory is" in verbose_log_contents
-    assert (
-        "Using GPU 0 to transfer data of shape (180, 128, 160)" in verbose_log_contents
-    )
+    assert "Using GPU 0 to transfer data of shape" in verbose_log_contents
 
 
 # TODO: rewrite and move to test_pipeline_big