mb2hal tests: ignore QUIT signal delivery time

This is the same change made to the old test in 2.8, applied to the new
test in 2.9: Don't look for SIGQUIT to be delivered at a specific time
in the log, there's some natural variability there.  We still look for
the other "quit" messages, which do have well-defined order.

Author: SebKuzminsky

tests/mb2hal/mb2hal.2a/checkresult

@@ -10,4 +10,9 @@ cd "${TESTDIR}"
 # so that a single `expected` file works for both.
 sed --in-place --regexp-extended --expression='s/^(.*unloading HAL module \[)[0-9]+(.*)$/\1(ignored comp id)\2/' result
 
+# The SIGQUIT signal does not arrive at a well-defined time, so don't
+# check for that debug log message.  The rest of the shutdown messages
+# seem to have well-defined order.
+sed --in-place --regexp-extended --expression='/^mb2hal quit_signal DEBUG: signal \[15\] received$/d' result
+
 diff -u expected result

tests/mb2hal/mb2hal.2a/expected

@@ -171,7 +171,6 @@ mb2hal create_each_mb_tx_hal_pins DEBUG: mb_tx_num [6] pin_name [mb2hal.Modbus_f
 mb2hal main OK: HAL components created OK
 mb2hal main OK: Link thread loop and logic 0 created OK
 mb2hal main OK: mb2hal is running
-mb2hal quit_signal DEBUG: signal [15] received
 mb2hal quit_cleanup DEBUG: started
 mb2hal quit_cleanup DEBUG: unloading HAL module [(ignored comp id)] ret[0]
 mb2hal quit_cleanup DEBUG: done OK