Revalidate the output after last change in surf messing with event order, and fix...

[simgrid.git] / teshsuite / gras / msg_handle / test_sg_64

diff --git a/teshsuite/gras/msg_handle/test_sg_64 b/teshsuite/gras/msg_handle/test_sg_64
index a2bcae7..ac7dfcc 100755 (executable)
--- a/teshsuite/gras/msg_handle/test_sg_64
+++ b/teshsuite/gras/msg_handle/test_sg_64
@@ -3,9 +3,9 @@ p Runs the 'msg_handle' test within the simulator (simulation times valid for 64
 $ $SG_TEST_EXENV gras/msg_handle/msg_handle_simulator$EXEEXT ${srcdir:=.}/../examples/msg/small_platform.xml ${srcdir:=.}/gras/msg_handle/msg_handle.xml
 > [Tremblay:server:(1) 0.000000] [test/INFO] Launch server (port=4000)
 > [Fafard:client:(2) 0.000000] [test/INFO] Launch client (port=4000)
-> [Tremblay:server:(1) 1.000000] [test/INFO] Initialization done.
-> [Tremblay:server:(1) 1.000000] [test/INFO] gras_msg_handle(0) works as expected (imediate timeout)
 > [Fafard:client:(2) 1.000000] [test/INFO] Initialization done.
+> [Tremblay:server:(1) 1.000000] [test/INFO] Initialization done.
+> [Tremblay:server:(1) 1.000000] [test/INFO] gras_msg_handle(0) works as expected (immediate timeout)
 > [Tremblay:server:(1) 2.000000] [test/INFO] gras_msg_handle(1) works as expected (delayed timeout)
 > [Tremblay:server:(1) 5.000000] [test/INFO] Unlock pal
 > [Tremblay:server:(1) 5.001976] [gras/INFO] Exiting GRAS