Oh wow! You responded!
Sorry, given my previous record on reporting bugs to RT, I was expecting
(at best) to hear something a few years from now.
So, changing `if ($^O =~ /bsd/) {` to `if ($^O =~ /bsd|darwin/) {` in
.../system-limits.PL and doing `make && make test` did the trick. B-)
Thus, if it helps, I can confirm setting
`$info{prefer_alt_alarm}`/`$PREFER_ALTERNATE_ALARM` to 1 on darwin fixes
the timeout test failures I originally reported.
Below is the resulting output for the .../t/40*-timeout.t tests:
t/40a-timeout.t ............... ok
t/40b-timeout.t ............... ok
t/40c-timeout.t ...............
Forks::Super::Job::_config_timeout_child(): quick timeout at
/Users/cal/build/Forks-Super-0.87/blib/lib/Forks/Super/Job.pm line 1947.
t/40c-timeout.t ............... ok
t/40d-timeout.t ............... ok
t/40e-timeout.t ............... ok
t/40f-timeout.t ...............
Forks::Super::Job::_config_timeout_child(): quick timeout at
/Users/cal/build/Forks-Super-0.87/blib/lib/Forks/Super/Job.pm line 1947.
t/40f-timeout.t ............... ok
t/40g-timeout.t ............... ok
t/40h-timeout.t ............... ok
t/40i-timeout.t ............... ok
t/40j-timeout.t ............... ok
Thanks for supporting your module!
~Cal
On Wed, Nov 23, 2016 at 9:29 PM, Marty O'Brien via RT <
bug-Forks-Super@rt.cpan.org> wrote:
Show quoted text> <URL:
https://rt.cpan.org/Ticket/Display.html?id=118474 >
>
> In the test report, t/40j-timeout.t passes but t/40a-timeout.t,
> t/40d-timeout.t,
> and t/40g-timeout.t all fail. This indicates that your system would
> benefit from
> using the "poor man's alarm", so I will enable it for all darwin users in
> v0.88.
>
> -- Marty
>
>
>