http://www.perlmonks.org?node_id=1214013


in reply to Re^7: Polite way to ask status of bug regarding Time::HiRes and newer versions of Perl
in thread Polite way to ask status of bug regarding Time::HiRes and newer versions of Perl

That's cool. But as I mentioned earlier in this thread, I am getting intermittent failures when installing (and testing) Time::HiRes v1.9758. It installs OK about half the time, and about half the time I get the stat.t error I showed, with the result time a second off from the expected value. For that reason, until I learned more about this, I would be wary of relying on Time::HiRes on a Macbook.


The way forward always starts with a minimal test.

Replies are listed 'Best First'.
Re^9: Polite way to ask status of bug regarding Time::HiRes and newer versions of Perl
by Your Mother (Archbishop) on May 03, 2018 at 16:46 UTC

    I think this is terrific advice in general. I just want to add an anecdote. Since the OS X beta 18 years ago I have had trouble on and off with certain CPAN packages (and plenty of other things really) on Mac; I never once got DBD::mysql to install clean. I resorted to --notest or --force a few times. And while there were definitely problems with test suites, I never had a "production" failure in one of my scripts running normally. I'm not advocating this for an actual production environment but just to say for my personal use OS X's ticks and version to version problems were mostly just cosmetic and things like Alien::SDL that were truly broken on OS X would not even --force install.