Bug #128599 for IPC-ShareLite: t/sharelite.t fails with perl-5.29.8

> > Each month I test the top 3000 distributions in the CPAN river against > > the latest Perl 5 monthly development release. The test is conducted > > on > > FreeBSD-11 and uses cpanm to try to install modules in dependency > > order. > > > > ##### > > $ uname -mrs > > FreeBSD 11.1-RELEASE amd64 > > ##### > > > > While testing perl-5.29.8 earlier this week I observed the following > > failure in IPC-ShareLite's test suite: > > > > ##### > > { > > author => "ANDYA", > > dist => "IPC-ShareLite", > > distname => "IPC-ShareLite-0.17", > > distversion => 0.17, > > grade => "FAIL", > > prereqs => undef, > > test_output => [ > > "Building and testing IPC-ShareLite-0.17", > > "cp lib/IPC/ShareLite.pm blib/lib/IPC/ShareLite.pm", > > "AutoSplitting blib/lib/IPC/ShareLite.pm > > (blib/lib/auto/IPC/ShareLite)", > > "Running Mkbootstrap for ShareLite ()", > > "chmod 644 \"ShareLite.bs\"", > > "\"/usr/home/jkeenan/var/tad/testing/perl-5.29.8/bin/perl\" > > -MExtUtils::Command::MM -e 'cp_nonempty' -- ShareLite.bs > > blib/arch/auto/IPC/ShareLite/ShareLite.bs 644", > > "cc -c -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H > > -fno-strict-aliasing -pipe -fstack-protector-strong > > -I/usr/local/include > > -D_FORTIFY_SOURCE=2 -O2 -pipe -fstack-protector -fno-strict-aliasing > > -DVERSION=\\\"0.17\\\" -DXS_VERSION=\\\"0.17\\\" -DPIC -fPIC > > \"-I/home/jkeenan/var/tad/testing/perl-5.29.8/lib/5.29.8/amd64- > > freebsd-thread-multi/CORE\" > > sharestuff.c", > > "\"/usr/home/jkeenan/var/tad/testing/perl-5.29.8/bin/perl\" > > \"/home/jkeenan/var/tad/testing/perl- > > 5.29.8/lib/5.29.8/ExtUtils/xsubpp\" > > -typemap > > '/home/jkeenan/var/tad/testing/perl- > > 5.29.8/lib/5.29.8/ExtUtils/typemap' > > -typemap > > '/usr/home/jkeenan/var/tad/testing/perl- > > 5.29.8/.cpanm/work/1550768645.33532/IPC-ShareLite-0.17/typemap' > > ShareLite.xs > ShareLite.xsc", > > "mv ShareLite.xsc ShareLite.c", > > "cc -c -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H > > -fno-strict-aliasing -pipe -fstack-protector-strong > > -I/usr/local/include > > -D_FORTIFY_SOURCE=2 -O2 -pipe -fstack-protector -fno-strict-aliasing > > -DVERSION=\\\"0.17\\\" -DXS_VERSION=\\\"0.17\\\" -DPIC -fPIC > > \"-I/home/jkeenan/var/tad/testing/perl-5.29.8/lib/5.29.8/amd64- > > freebsd-thread-multi/CORE\" > > ShareLite.c", > > "rm -f blib/arch/auto/IPC/ShareLite/ShareLite.so", > > "cc -shared -L/usr/local/lib -fstack-protector-strong > > sharestuff.o ShareLite.o -o > > blib/arch/auto/IPC/ShareLite/ShareLite.so > > ", > > "chmod 755 blib/arch/auto/IPC/ShareLite/ShareLite.so", > > "\"/usr/home/jkeenan/var/tad/testing/perl-5.29.8/bin/perl\" > > -MExtUtils::Command::MM -e 'cp_nonempty' -- ShareLite.bs > > blib/arch/auto/IPC/ShareLite/ShareLite.bs 644", > > "PERL_DL_NONLAZY=1 > > \"/usr/home/jkeenan/var/tad/testing/perl-5.29.8/bin/perl\" > > \"-MExtUtils::Command::MM\" \"-MTest::Harness\" \"-e\" \"undef > > *Test::Harness::Switches; test_harness(0, 'blib/lib', 'blib/arch')\" > > t/*.t", > > "# Testing IPC::ShareLite 0.17", > > "t/00-load.t ...... ok", > > "t/pod.t .......... ok", > > "Failed to create share at t/sharelite.t line 18.", > > "# Looks like your test exited with 28 just after 1.", > > "t/sharelite.t .... ", > > "Dubious, test returned 28 (wstat 7168, 0x1c00)", > > "Failed 13/14 subtests ", > > "t/unicode-key.t .. ok", > > "", > > "Test Summary Report", > > "-------------------", > > "t/sharelite.t (Wstat: 7168 Tests: 1 Failed: 0)", > > " Non-zero exit status: 28", > > " Parse errors: Bad plan. You planned 14 tests but ran 1.", > > "Files=4, Tests=6, 0 wallclock secs ( 0.02 usr 0.02 sys + > > 0.32 > > cusr 0.14 csys = 0.49 CPU)", > > "Result: FAIL", > > ], > > via => "App::cpanminus::reporter 0.17 (1.7044)", > > } > > ##### > > > > I was able to reproduce this failure manually by running 'make test' > > in > > the relevant .cpanm/latest-build subdirectory. > > > > This failure has also begun to appear in CPANtesters reports. See, > > e.g., this failure on OpenBSD: > > > > http://www.cpantesters.org/cpan/report/ca588786-2bef-11e9-a40e- > > 9d25b8c74ba8 > > > > In my FreeBSD testing environment this failure did not appear in > > perl-5.29.7 (Jan 2019). I have not yet been able to diagnose the > > cause > > of the test failure.