Bug#952158: pkwalify: FTBFS: dh_auto_test: error: make -j1 test TEST_VERBOSE=1 returned exit code 2

[Lucas Nussbaum]

Source: pkwalify
Version: 1.22.99~git3d3f0ea-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye

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/compat.t ....... 
> 1..2
> # Running under perl version 5.030000 for linux
> # Current time local: Sun Feb 23 02:53:08 2020
> # Current time GMT:   Sun Feb 23 02:53:08 2020
> # Using Test.pm version 1.31
> ok 1
> ok 2
> ok
> [/mapping/recursive_hash/name] Expected subschema (a hash)
> # Looks like your test exited with 2 just after 38.
> t/Kwalify.t ...... 
> 1..100
> ok 1 - use Kwalify;
> ok 2 - use Schema::Kwalify;
> ok 3 - sequence of str
> ok 4 - sequence with default type (str)
> ok 5 - Non valid data, int in sequence of str
> ok 6
> ok 7 - mapping
> ok 8 - invalid mapping
> ok 9
> ok 10
> ok 11
> ok 12 - sequence of mapping
> ok 13
> ok 14
> ok 15
> ok 16
> ok 17 - mapping of sequence
> ok 18
> ok 19
> ok 20
> ok 21 - Many rules
> ok 22
> ok 23
> ok 24
> ok 25
> ok 26
> ok 27
> ok 28
> ok 29
> ok 30
> ok 31
> ok 32
> ok 33 - unique
> ok 34
> ok 35
> ok 36
> ok 37
> ok 38
> Dubious, test returned 2 (wstat 512, 0x200)
> Failed 62/100 subtests 
> t/pkwalify.t ..... 
> 1..31
> ok 1 - No warnings in -f /<<PKGBUILDDIR>>/t/testdata/schema05.yaml /<<PKGBUILDDIR>>/t/testdata/document05a.yaml
> ok 2 - Nothing in STDERR
> ok 3 - -f /<<PKGBUILDDIR>>/t/testdata/schema05.yaml /<<PKGBUILDDIR>>/t/testdata/document05a.yaml
> ok 4 - There are warnings in -f /<<PKGBUILDDIR>>/t/testdata/schema05.yaml /<<PKGBUILDDIR>>/t/testdata/document05b.yaml
> ok 5 - Nothing in STDERR
> ok 6 - -f /<<PKGBUILDDIR>>/t/testdata/schema05.yaml /<<PKGBUILDDIR>>/t/testdata/document05b.yaml
> ok 7 - There are warnings in -f /tmp/QV38FfTp6i.yaml /<<PKGBUILDDIR>>/t/testdata/document05a.yaml
> ok 8 - Nothing in STDERR
> ok 9 - -f /tmp/QV38FfTp6i.yaml /<<PKGBUILDDIR>>/t/testdata/document05a.yaml
> ok 10 - There are warnings in -f /<<PKGBUILDDIR>>/t/testdata/schema05.yaml /tmp/6JFDIqePS6.yaml
> ok 11 - Nothing in STDERR
> ok 12 - -f /<<PKGBUILDDIR>>/t/testdata/schema05.yaml /tmp/6JFDIqePS6.yaml
> ok 13 - No warnings in -f /<<PKGBUILDDIR>>/t/testdata/schema05.yaml /tmp/FJpq_6CJwN.yaml
> ok 14 - Nothing in STDERR
> ok 15 - -f /<<PKGBUILDDIR>>/t/testdata/schema05.yaml /tmp/FJpq_6CJwN.yaml
> ok 16 - There are warnings in -f /<<PKGBUILDDIR>>/t/testdata/schema05.yaml /tmp/tMs89tttnt.yaml
> ok 17 - Nothing in STDERR
> ok 18 - -f /<<PKGBUILDDIR>>/t/testdata/schema05.yaml /tmp/tMs89tttnt.yaml
> ok 19 - No success without options
> ok 20 - usage -f
> ok 21 - Invalid option
> ok 22 - got usage
> ok 23 - Missing data file
> ok 24 - usage datafile
> ok 25 - No YAML/JSON file
> ok 26 - cannot parse file
> ok 27 - Success with -s
> ok 28 - silent output
> ok 29 - Success without -s
> ok 30 - non-silent output for validity
> ok 31 - /<<PKGBUILDDIR>>/t/../blib/script/pkwalify compiles OK
> ok
> t/required-no.t .. 
> 1..1
> ok 1
> ok
> 
> Test Summary Report
> -------------------
> t/Kwalify.t    (Wstat: 512 Tests: 38 Failed: 0)
>   Non-zero exit status: 2
>   Parse errors: Bad plan.  You planned 100 tests but ran 38.
> Files=4, Tests=72,  1 wallclock secs ( 0.03 usr  0.00 sys +  0.42 cusr  0.07 csys =  0.52 CPU)
> Result: FAIL
> Failed 1/4 test programs. 0/72 subtests failed.
> make[1]: *** [Makefile:852: test_dynamic] Error 255
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> dh_auto_test: error: make -j1 test TEST_VERBOSE=1 returned exit code 2

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/pkwalify_1.22.99~git3d3f0ea-1_unstable.log

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!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.