[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#22130: dmd: respawn test failures
From: |
Ludovic Courtès |
Subject: |
bug#22130: dmd: respawn test failures |
Date: |
Wed, 06 Jan 2016 23:56:39 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) |
Mark H Weaver <address@hidden> skribis:
> + deco -s t-socket-759 status dmd
> Started: (test1 test2 dmd)
> Stopped: ()
> + grep started
> + deco -s t-socket-759 status test1
> It is started.
> + grep started
> + deco -s t-socket-759 status test2
> It is started.
> + test -f t-service1-pid-759
> + cat t-log-759
The problem here is that the PID file for ‘service1’ is not ready when
we ‘test -f’ it right after ‘deco status test1’ has told us the service
is started. That’s because there’s a small window during which the
service is started but has not created its PID file yet.
Fixed in dmd commit f33f81f.
We’ll backport it in Guix or make a dmd release.
Thanks,
Ludo’.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- bug#22130: dmd: respawn test failures,
Ludovic Courtès <=