| Subject: | Test fails when it possibly shouldn't (Forks-Super-0.7.6) |
| Date: | Sat, 11 Jul 2015 14:13:09 -0700 |
| To: | bug-Forks-Super [...] rt.cpan.org |
| From: | Paul Nelson <paulnelson54321 [...] gmail.com> |
Forks-Super-0.7.6
log:
# Failed test 'daemon process does not have a parent'
# at t/66a-daemon.t line 106.
# daemon process was '3046
# ', expected '1'
# Looks like you failed 1 test of 8.
t/66a-daemon.t ...............
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/8 subtests
On line 106, test 5, it checks for the daemon's parent to be 1 i.e. true
init. But actual parent was 3046 which at the time of running was an 'init
--user' launched by my display manager.
init :: pid 1
|
Show quoted text
> lightdm (display manager) :: pid *
|
Show quoted text> lightdm :: pid *
|
Show quoted text> init --user :: pid 3046
|
Show quoted text > perl :: pid *
Dropped to TTY1 and it tested and installed correctly. Some secondary tests
with forking daemons in all C confirmed that in the TTY daemons get ppid 1
correctly.
Easy enough, but a few other bug reports reference this issue so I thought
I'd share.
http://www.cpantesters.org/cpan/report/fb99a624-642d-11e4-827f-be4ef0f5f41a
Perhaps the test on t/66a-daemon.t:106 (5th test) can be changed to also
succeed if daemon ppid is of any init process. (or the nearest parent to us
in proc hierarchy).
I'm running 64 bit perl v5.18.2 :: Lubuntu 14.04 linux 4.1.1
Linux pjnlubuntu 4.1-1.dmz.2-liquorix-amd64 #1 ZEN SMP PREEMPT Debian 4.1-2
(2015-07-05) x86_64 x86_64 x86_64 GNU/Linux