Bug#742970: the package FTBFS due to failing tests right now.
I recently found that round tuit that had something to do with
using Object::Remote in a project and proceeded to build the package.
Unfortunately, it fails to build due to some failing tests and I have no
idea how to fix this... other than downgrading libfuture-perl to
something << 0.26 as described in
<https://rt.cpan.org/Public/Bug/Display.html?id=96333>.
Cheers,
-Hilko
dpkg-buildpackage: source package libobject-remote-perl
dpkg-buildpackage: source version 0.003002-1
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by Hilko Bengen <bengen@debian.org>
dpkg-buildpackage: host architecture amd64
dpkg-source --before-build libobject-remote-perl
fakeroot debian/rules clean
dh clean
dh_testdir
dh_auto_clean
make[1]: Entering directory '/home/bengen/src/deb/perl/libobject-remote-perl'
rm -f \
blib/script/object-remote-node blib/script/remoterepl \
blib/script/object-remote-slave
rm -f \
blibdirs.ts *.a \
MYMETA.yml pm_to_blib.ts \
blib/arch/auto/Object/Remote/extralibs.all perl \
Makefile.aperl pm_to_blib \
core.*perl.*.? \
tmon.out perlmain.c \
Remote.bso core.[0-9] \
Remote.exp libRemote.def \
*perl.core MYMETA.json \
perl core.[0-9][0-9] \
perl.exe Remote.def \
so_locations core \
blib/arch/auto/Object/Remote/extralibs.ld core.[0-9][0-9][0-9] \
core.[0-9][0-9][0-9][0-9][0-9] mon.out \
Remote.x *.o \
core.[0-9][0-9][0-9][0-9]
rm -rf \
blib
mv Makefile Makefile.old > /dev/null 2>&1
rm -f \
Makefile.old Makefile
rm -rf \
Object-Remote-0.003002
/usr/bin/perl "-MExtUtils::Manifest=fullcheck" -e fullcheck
Not in MANIFEST: debian/changelog
Not in MANIFEST: debian/compat
Not in MANIFEST: debian/control
Not in MANIFEST: debian/copyright
Not in MANIFEST: debian/libobject-remote-perl.debhelper.log
Not in MANIFEST: debian/rules
Not in MANIFEST: debian/source/format
Not in MANIFEST: debian/watch
make[1]: Leaving directory '/home/bengen/src/deb/perl/libobject-remote-perl'
dh_clean
debian/rules build
dh build
dh_testdir
dh_auto_configure
Checking if your kit is complete...
Looks good
Writing Makefile for Object::Remote
Writing MYMETA.yml and MYMETA.json
dh_auto_build
make[1]: Entering directory '/home/bengen/src/deb/perl/libobject-remote-perl'
cp lib/Object/Remote/MiniLoop.pm blib/lib/Object/Remote/MiniLoop.pm
cp lib/Object/Remote/Null.pm blib/lib/Object/Remote/Null.pm
cp lib/Object/Remote/WatchDog.pm blib/lib/Object/Remote/WatchDog.pm
cp lib/Object/Remote/Role/LogForwarder.pm blib/lib/Object/Remote/Role/LogForwarder.pm
cp lib/Object/Remote/ModuleSender.pm blib/lib/Object/Remote/ModuleSender.pm
cp lib/Object/Remote/Prompt.pm blib/lib/Object/Remote/Prompt.pm
cp lib/Object/Remote/CodeContainer.pm blib/lib/Object/Remote/CodeContainer.pm
cp lib/Object/Remote/Node.pm blib/lib/Object/Remote/Node.pm
cp lib/Object/Remote/ConnectionServer.pm blib/lib/Object/Remote/ConnectionServer.pm
cp lib/Object/Remote/Proxy.pm blib/lib/Object/Remote/Proxy.pm
cp lib/Object/Remote/Logging/LogAnyInjector.pm blib/lib/Object/Remote/Logging/LogAnyInjector.pm
cp lib/Object/Remote/Role/Connector/PerlInterpreter.pm blib/lib/Object/Remote/Role/Connector/PerlInterpreter.pm
cp lib/Object/Remote/Logging/TestLogger.pm blib/lib/Object/Remote/Logging/TestLogger.pm
cp lib/Object/Remote/Tied.pm blib/lib/Object/Remote/Tied.pm
cp lib/Object/Remote/FatNode.pm blib/lib/Object/Remote/FatNode.pm
cp lib/Object/Remote/ModuleLoader.pm blib/lib/Object/Remote/ModuleLoader.pm
cp lib/Object/Remote/Logging/Router.pm blib/lib/Object/Remote/Logging/Router.pm
cp lib/Object/Remote/Logging.pm blib/lib/Object/Remote/Logging.pm
cp lib/Object/Remote/ReadChannel.pm blib/lib/Object/Remote/ReadChannel.pm
cp lib/Object/Remote/Connector/Local.pm blib/lib/Object/Remote/Connector/Local.pm
cp lib/Object/Remote/Future.pm blib/lib/Object/Remote/Future.pm
cp lib/Object/Remote/Connector/SSH.pm blib/lib/Object/Remote/Connector/SSH.pm
cp lib/Object/Remote/Logging/Logger.pm blib/lib/Object/Remote/Logging/Logger.pm
cp lib/Object/Remote/Connector/UNIX.pm blib/lib/Object/Remote/Connector/UNIX.pm
cp lib/Object/Remote/GlobContainer.pm blib/lib/Object/Remote/GlobContainer.pm
cp lib/Object/Remote/Role/Connector.pm blib/lib/Object/Remote/Role/Connector.pm
cp lib/Object/Remote/Connector/LocalSudo.pm blib/lib/Object/Remote/Connector/LocalSudo.pm
cp lib/Object/Remote.pm blib/lib/Object/Remote.pm
cp lib/Object/Remote/GlobProxy.pm blib/lib/Object/Remote/GlobProxy.pm
cp lib/Object/Remote/Handle.pm blib/lib/Object/Remote/Handle.pm
cp lib/Object/Remote/Connector/STDIO.pm blib/lib/Object/Remote/Connector/STDIO.pm
cp lib/Object/Remote/Connection.pm blib/lib/Object/Remote/Connection.pm
cp lib/Object/Remote/FromData.pm blib/lib/Object/Remote/FromData.pm
cp bin/object-remote-node blib/script/object-remote-node
/usr/bin/perl -MExtUtils::MY -e 'MY->fixin(shift)' -- blib/script/object-remote-node
cp bin/object-remote-slave blib/script/object-remote-slave
/usr/bin/perl -MExtUtils::MY -e 'MY->fixin(shift)' -- blib/script/object-remote-slave
cp bin/remoterepl blib/script/remoterepl
/usr/bin/perl -MExtUtils::MY -e 'MY->fixin(shift)' -- blib/script/remoterepl
Manifying blib/man3/Object::Remote::Logging.3pm
Manifying blib/man3/Object::Remote::Role::Connector::PerlInterpreter.3pm
Manifying blib/man3/Object::Remote::Logging::Logger.3pm
Manifying blib/man3/Object::Remote.3pm
Manifying blib/man3/Object::Remote::Connection.3pm
Manifying blib/man3/Object::Remote::Future.3pm
make[1]: Leaving directory '/home/bengen/src/deb/perl/libobject-remote-perl'
dh_auto_test
make[1]: Entering directory '/home/bengen/src/deb/perl/libobject-remote-perl'
PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
t/await.t ............. ok
t/basic.t ............. ok
t/basic_data.t ........ ok
t/bridged.t ........... ok
t/chained.t ........... ok
t/logger.t ............ ok
t/logging.t ........... ok
t/logrouter.t ......... ok
t/objects.t ........... ok
t/perl_execute.t ...... ok
t/sender.t ............ ok
t/start_core.t ........ 1/? Future=HASH(0x1066a00) Future=HASH(0x1066a00) lost a sequence Future at t/start_core.t line 33.
# Failed test 'Second future constructed after first future completed'
# at t/start_core.t line 78.
Can't use an undefined value as a subroutine reference at t/start_core.t line 82.
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 255 just after 4.
t/start_core.t ........ Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 1/4 subtests
t/tied.t .............. ok
t/timeout.t ........... ok
t/transfer.t .......... ok
t/watchdog.t .......... ok
t/watchdog_fatnode.t .. ok
Test Summary Report
-------------------
t/start_core.t (Wstat: 65280 Tests: 4 Failed: 1)
Failed test: 3
Non-zero exit status: 255
Parse errors: No plan found in TAP output
Files=17, Tests=121, 23 wallclock secs ( 0.16 usr 0.04 sys + 6.70 cusr 0.75 csys = 7.65 CPU)
Result: FAIL
Failed 1/17 test programs. 1/121 subtests failed.
Makefile:958: recipe for target 'test_dynamic' failed
make[1]: *** [test_dynamic] Error 255
make[1]: Leaving directory '/home/bengen/src/deb/perl/libobject-remote-perl'
dh_auto_test: make -j1 test returned exit code 2
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
Reply to: