#! ./tesh
-p Testing a simple master/slave example application
-
-$ $SG_TEST_EXENV parallel_task/parallel_task$EXEEXT ${srcdir:=.}/small_platform.xml
-> [0.000000] [xbt_cfg/INFO] type in variable = 2
-> [Ginette:test:(1) 0.009378] [msg_test/INFO] Goodbye now!
-> [0.009378] [msg_test/INFO] Simulation time 0.00937836
-
-$ $SG_TEST_EXENV parallel_task/test_ptask$EXEEXT ${srcdir:=.}/parallel_task/test_ptask_platform.xml ${srcdir:=.}/parallel_task/test_ptask_deployment.xml
-> [0.000000] [xbt_cfg/INFO] type in variable = 2
-> [Ginette:execute:(1) 1.000300] [msg_test/INFO] execution_time=1.0003
-> [Ginette:redistribute:(2) 6.000900] [msg_test/INFO] redistribution_time=6.0009
-> [6.000900] [msg_test/INFO] Simulation time 6.0009
+$ $SG_TEST_EXENV parallel_task/parallel_task$EXEEXT ${srcdir:=.}/../platforms/small_platform.xml "--log=root.fmt:[%10.6r]%e(%i:%P@%h)%e%m%n"
+> [ 0.000000] (0:maestro@) Switching to the L07 model to handle parallel tasks.
+> [ 0.000000] (1:test@Fafard) First, build a classical parallel task, with 1 Gflop to execute on each node, and 10MB to exchange between each pair
+> [ 20.625396] (1:test@Fafard) Then, build a parallel task involving only computations and no communication (1 Gflop per node)
+> [ 41.247354] (1:test@Fafard) Finally, trick the ptask to do a 'remote execution', on host Tremblay
+> [ 51.441554] (1:test@Fafard) Goodbye now!
+> [ 51.441554] (0:maestro@) Simulation done.
