You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With a big emphasis on occasionally, borderline never. Feel free to close this and consider it as just informative, since there isn't much to fix.
This is on Android 2.3.3, on relatively old hardware (armv7 1024 MHz processor, 300MB RAM), perl 5.19.9 (blead as of yesterday). The test file looks simple enough, so it's probably the alarm() firing off too quickly/too late on this processor.
The text was updated successfully, but these errors were encountered:
While doing some research for the fail report http://www.cpantesters.org/cpan/report/3edc5590-8cbd-11e5-a3d8-5587f83dfc95 (which does not hang, but fails in the same test script), I managed to produce a hang on a "normal" Linux system. For this I had to hack the test script to use a shorter alarm value, something like Time::HiRes::alarm(0.002). It seems that under some circumstances, if SIGALRM is delivered while dynamically loading File::Find and its dependencies, the signal handler never gets called. Here's an strace log showing this situation. Perl was started with "unsafe signals" here (PERL_SIGNALS=unsafe), but it happens with safe signals, too:
With a big emphasis on occasionally, borderline never. Feel free to close this and consider it as just informative, since there isn't much to fix.
This is on Android 2.3.3, on relatively old hardware (armv7 1024 MHz processor, 300MB RAM), perl 5.19.9 (blead as of yesterday). The test file looks simple enough, so it's probably the alarm() firing off too quickly/too late on this processor.
The text was updated successfully, but these errors were encountered: