Hello, Mark H Weaver <m...@netris.org> skribis:
> However, on armhf-linux, three tests failed: respawn.sh, > respawn-throttling.sh, and pid-file.sh. > > https://hydra.gnu.org/build/2499835 (Similar issue on aarch64: <https://berlin.guixsd.org/build/2419870/log/raw>. Though of course it passed on the 2nd and 3rd attempts…) I was able to reproduce a tests/respawn.sh failure on hardware (ARMv7). The issue is that a service is not respawned, and the log shows: --8<---------------cut here---------------start------------->8--- + assert_killed_service_is_respawned t-service2-pid-695 ++ cat t-service2-pid-695 + old_pid=789 + rm t-service2-pid-695 + kill 789 + wait_for_file t-service2-pid-695 + i=0 + test -f t-service2-pid-695 + test 0 -lt 20 + sleep 0.3 ++ expr 0 + 1 [...] 2018-02-16 11:13:31 Service root has been started. 2018-02-16 11:13:32 Service test1 has been started. 2018-02-16 11:13:34 Service test2 has been started. 2018-02-16 11:13:35 Respawning test1. 2018-02-16 11:13:35 Service test1 has been started. 2018-02-16 11:13:36 Respawning test2. 2018-02-16 11:13:37 Service test2 has been started. 2018-02-16 11:13:37 Respawning test1. 2018-02-16 11:13:37 Service test1 has been started. 2018-02-16 11:13:38 Respawning test2. 2018-02-16 11:13:43 Service test2 could not be started. --8<---------------cut here---------------end--------------->8--- So SIGCHLD was correctly delivered, but somehow restarting that service didn’t work (its PID file didn’t show up again; the 5 seconds between “Respawning” and “could not be started” correspond to the delay in ‘read-pid-file’ in (shepherd service)). These test failures seem to be more frequent when the machine is loaded. Ludo’.
