Bug#1016313: liblexical-accessor-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2

[Lucas Nussbaum]

Source: liblexical-accessor-perl
Version: 0.013-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lucas at debian.org
Usertags: ftbfs-20220728 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 'blib/arch')" t/*.t
> t/01basic.t ........ 
> ok 1 - use Lexical::Accessor;
> 1..1
> ok
> t/02moose.t ........ 
> ok 1 - predicate
> ok 2 - predicate
> ok 3 - setter makes value visible to predicate
> ok 4 - ... does not mix up objects
> ok 5 - ... and visible to accessor called as getter
> ok 6 - ... does not mix up objects
> ok 7 - ... and visible to reader
> ok 8 - ... does not mix up objects
> ok 9 - accessor called as setter makes value visible to predicate
> ok 10 - ... does not mix up objects
> ok 11 - ... and visible to accessor called as getter
> ok 12 - ... does not mix up objects
> ok 13 - ... and visible to reader
> ok 14 - ... does not mix up objects
> ok 15 - clearer
> ok 16 - ... does not mix up objects
> ok 17 - triggers work
> ok 18 - no leaks
> ok 19 - correct accessor returned for is => rw
> ok 20 - correct getter returned for is => ro
> ok 21 - correct getter returned for is => rwp
> ok 22 - correct setter returned for is => rwp
> ok 23 - correct reader returned for is => lazy
> 1..23
> ok
> t/03mouse.t ........ 
> ok 1 - predicate
> ok 2 - predicate
> ok 3 - setter makes value visible to predicate
> ok 4 - ... does not mix up objects
> ok 5 - ... and visible to accessor called as getter
> ok 6 - ... does not mix up objects
> ok 7 - ... and visible to reader
> ok 8 - ... does not mix up objects
> ok 9 - accessor called as setter makes value visible to predicate
> ok 10 - ... does not mix up objects
> ok 11 - ... and visible to accessor called as getter
> ok 12 - ... does not mix up objects
> ok 13 - ... and visible to reader
> ok 14 - ... does not mix up objects
> ok 15 - clearer
> ok 16 - ... does not mix up objects
> ok 17 - triggers work
> ok 18 - no leaks
> ok 19 - correct accessor returned for is => rw
> ok 20 - correct getter returned for is => ro
> ok 21 - correct getter returned for is => rwp
> ok 22 - correct setter returned for is => rwp
> ok 23 - correct reader returned for is => lazy
> 1..23
> ok
> t/04moo.t .......... 
> ok 1 - predicate
> ok 2 - predicate
> ok 3 - setter makes value visible to predicate
> ok 4 - ... does not mix up objects
> ok 5 - ... and visible to accessor called as getter
> ok 6 - ... does not mix up objects
> ok 7 - ... and visible to reader
> ok 8 - ... does not mix up objects
> ok 9 - accessor called as setter makes value visible to predicate
> ok 10 - ... does not mix up objects
> ok 11 - ... and visible to accessor called as getter
> ok 12 - ... does not mix up objects
> ok 13 - ... and visible to reader
> ok 14 - ... does not mix up objects
> ok 15 - clearer
> ok 16 - ... does not mix up objects
> ok 17 - triggers work
> ok 18 - no leaks
> ok 19 - correct accessor returned for is => rw
> ok 20 - correct getter returned for is => ro
> ok 21 - correct getter returned for is => rwp
> ok 22 - correct setter returned for is => rwp
> ok 23 - correct reader returned for is => lazy
> 1..23
> ok
> t/05classtiny.t .... 
> ok 1 - predicate
> ok 2 - predicate
> ok 3 - setter makes value visible to predicate
> ok 4 - ... does not mix up objects
> ok 5 - ... and visible to accessor called as getter
> ok 6 - ... does not mix up objects
> ok 7 - ... and visible to reader
> ok 8 - ... does not mix up objects
> ok 9 - accessor called as setter makes value visible to predicate
> ok 10 - ... does not mix up objects
> ok 11 - ... and visible to accessor called as getter
> ok 12 - ... does not mix up objects
> ok 13 - ... and visible to reader
> ok 14 - ... does not mix up objects
> ok 15 - clearer
> ok 16 - ... does not mix up objects
> ok 17 - triggers work
> ok 18 - no leaks
> ok 19 - correct accessor returned for is => rw
> ok 20 - correct getter returned for is => ro
> ok 21 - correct getter returned for is => rwp
> ok 22 - correct setter returned for is => rwp
> ok 23 - correct reader returned for is => lazy
> 1..23
> ok
> Can't locate object method "make_callbacks" via package "Sub::HandlesVia::Toolkit::Plain" at /<<PKGBUILDDIR>>/blib/lib/Sub/Accessor/Small.pm line 117.
> t/30shv.t .......... 
> Dubious, test returned 255 (wstat 65280, 0xff00)
> No subtests run 
> t/90subclassing.t .. 
> ok 1
> ok 2
> ok 3
> 1..3
> ok
> t/rt101024.t ....... 
> ok 1
> 1..1
> ok
> 
> Test Summary Report
> -------------------
> t/30shv.t        (Wstat: 65280 Tests: 0 Failed: 0)
>   Non-zero exit status: 255
>   Parse errors: No plan found in TAP output
> Files=8, Tests=97,  1 wallclock secs ( 0.04 usr  0.01 sys +  0.90 cusr  0.08 csys =  1.03 CPU)
> Result: FAIL
> Failed 1/8 test programs. 0/97 subtests failed.
> make[1]: *** [Makefile:843: test_dynamic] Error 255
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2


The full build log is available from:
http://qa-logs.debian.net/2022/07/28/liblexical-accessor-perl_0.013-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220728;users=lucas@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220728&fusertaguser=lucas@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.