Package: src:libtest-fitesque-rdf-perl
Version: 0.100-1
Severity: serious
Tags: ftbfs trixie sid
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
--------------------------------------------------------------------------------
[...]
debian/rules clean
dh clean
dh_clean
debian/rules binary
dh binary
dh_update_autotools_config
dh_autoreconf
dh_auto_configure
/usr/bin/perl Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2
-Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2"
"LD=x86_64-linux-gnu-gcc -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
-Wl,-z,relro"
Checking if your kit is complete...
Looks good
Generating a Unix-style Makefile
Writing Makefile for Test::FITesque::RDF
Writing MYMETA.yml and MYMETA.json
dh_auto_build
make -j2
make[1]: Entering directory '/<<PKGBUILDDIR>>'
cp lib/Test/FITesque/RDF.pm blib/lib/Test/FITesque/RDF.pm
Manifying 1 pod document
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
debian/rules override_dh_auto_test
make[1]: Entering directory '/<<PKGBUILDDIR>>'
# suppress DNS queries
RES_OPTIONS=attempts:0 dh_auto_test
make -j2 test TEST_VERBOSE=1
make[2]: 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
# Testing Test::FITesque::RDF 0.10, Perl 5.040000, /usr/bin/perl
t/01basic.t ................
ok 1 - use Test::FITesque::RDF;
1..1
ok
Overwriting existing sub 'main::done_testing' with sub 'done_testing' exported
by Test::Modern at t/integration-basic.t line 29.
# Failed test 'no (unexpected) warnings (via done_testing)'
# at t/integration-basic.t line 82.
# Looks like you failed 1 test of 7.
t/integration-basic.t ......
ok 1 - use Test::FITesque::RDF;
# Subtest: Run with no file
ok 1 - Failed due to missing file
1..1
ok 2 - Run with no file
# Subtest: Run with invalid file
ok 1 - Failed correctly due to parse error
1..1
ok 3 - Run with invalid file
# Subtest: Run with no tests file
ok 1 - Failed correctly due to no test error
1..1
ok 4 - Run with no tests file
# Subtest: Run with no descriptions in file
ok 1 - Failed correctly due to undescribed test error
1..1
ok 5 - Run with no descriptions in file
# Subtest: Test multiple tests
1..8
# Multiply two numbers
ok 1 - Factor 1 exists
ok 2 - Factor 2 exists
ok 3 - Product parameter exists
ok 4 - Product is correct
# Echo a string
ok 5 - String exists
ok 6 - Has a certain keyword
# Run with no param_base
ok 7 - String exists
ok 8 - Has a certain keyword
ok 6 - Test multiple tests
not ok 7 - no (unexpected) warnings (via done_testing)
1..7
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/7 subtests
t/integration-http-list.t ..
1..6
# More elaborate HTTP vocab for PUT then GET test
ok 1 - There are two request-response pairs
ok 2 - First method is PUT
ok 3 - Second method is GET
ok 4 - First code is 201
ok 5 - Second ctype is turtle
ok 6 - Response header field value bag comparison
ok
t/unit-http-list.t .........
# Subtest: RDF Fixture object ok
ok 1 - instantiate RDF Fixture object
ok 2 - RDF Fixture object is blessed
ok 3 - 'RDF Fixture object' isa 'Test::FITesque::RDF'
ok 4 - 'RDF Fixture object' isa 'Moo::Object'
ok 5 - Test::FITesque::RDF->can(...)
1..5
ok 1 - RDF Fixture object ok
ok 2 - Main structure ok
ok 3 - There are two request-response pairs
# Subtest: Checking request object ok
ok 1 - Checking request object is blessed
ok 2 - 'Checking request object' isa 'HTTP::Request'
ok 3 - HTTP::Request->can(...)
1..3
ok 4 - Checking request object ok
# Subtest: Checking response object ok
ok 1 - Checking response object is blessed
ok 2 - 'Checking response object' isa 'HTTP::Response'
ok 3 - HTTP::Response->can(...)
1..3
ok 5 - Checking response object ok
# Subtest: Checking request object ok
ok 1 - Checking request object is blessed
ok 2 - 'Checking request object' isa 'HTTP::Request'
ok 3 - HTTP::Request->can(...)
1..3
ok 6 - Checking request object ok
# Subtest: Checking response object ok
ok 1 - Checking response object is blessed
ok 2 - 'Checking response object' isa 'HTTP::Response'
ok 3 - HTTP::Response->can(...)
1..3
ok 7 - Checking response object ok
ok 8 - First method is PUT
ok 9 - Second method is GET
ok 10 - First request has content
ok 11 - First code is 201
ok 12 - Second ctype is turtle
ok 13 - Response header field value bag comparison can be used for single values
ok 14 - Response header field value bag comparison
ok 15 - no (unexpected) warnings (via done_testing)
1..15
ok
t/unit-http-mix.t ..........
# Subtest: RDF Fixture object ok
ok 1 - instantiate RDF Fixture object
ok 2 - RDF Fixture object is blessed
ok 3 - 'RDF Fixture object' isa 'Test::FITesque::RDF'
ok 4 - 'RDF Fixture object' isa 'Moo::Object'
ok 5 - Test::FITesque::RDF->can(...)
1..5
ok 1 - RDF Fixture object ok
ok 2 - Main structure ok
ok 3 - There is one request
# Subtest: Checking request object ok
ok 1 - Checking request object is blessed
ok 2 - 'Checking request object' isa 'HTTP::Request'
ok 3 - HTTP::Request->can(...)
1..3
ok 4 - Checking request object ok
ok 5 - no (unexpected) warnings (via done_testing)
1..5
ok
t/unit-http-regex.t ........
# Subtest: RDF Fixture object ok
ok 1 - instantiate RDF Fixture object
ok 2 - RDF Fixture object is blessed
ok 3 - 'RDF Fixture object' isa 'Test::FITesque::RDF'
ok 4 - 'RDF Fixture object' isa 'Moo::Object'
ok 5 - Test::FITesque::RDF->can(...)
1..5
ok 1 - RDF Fixture object ok
ok 2 - Main structure ok
ok 3 - There are three pairs
ok 4 - Should be single escaped
ok 5 - Status is correct
ok 6 - no (unexpected) warnings (via done_testing)
1..6
ok
t/unit-http-server.t .......
# Subtest: Invalid remote source
# Subtest: RDF Fixture object ok
ok 1 - instantiate RDF Fixture object
ok 2 - RDF Fixture object is blessed
ok 3 - 'RDF Fixture object' isa 'Test::FITesque::RDF'
ok 4 - 'RDF Fixture object' isa 'Moo::Object'
ok 5 - Test::FITesque::RDF->can(...)
1..5
ok 1 - RDF Fixture object ok
ok 2 - Failed to get from invalid host
1..2
ok 1 - Invalid remote source
# Subtest: Get content remotely
# Subtest: RDF Fixture object ok
ok 1 - instantiate RDF Fixture object
ok 2 - RDF Fixture object is blessed
ok 3 - 'RDF Fixture object' isa 'Test::FITesque::RDF'
ok 4 - 'RDF Fixture object' isa 'Moo::Object'
ok 5 - Test::FITesque::RDF->can(...)
1..5
ok 1 - RDF Fixture object ok
ok 2 - Main structure ok
ok 3 - There is request-response pair
# Subtest: Checking request object ok
ok 1 - Checking request object is blessed
ok 2 - 'Checking request object' isa 'HTTP::Request'
ok 3 - HTTP::Request->can(...)
1..3
ok 4 - Checking request object ok
# Subtest: Checking response object ok
ok 1 - Checking response object is blessed
ok 2 - 'Checking response object' isa 'HTTP::Response'
ok 3 - HTTP::Response->can(...)
1..3
ok 5 - Checking response object ok
ok 6 - First method is PUT
ok 7 - First request has content
1..7
ok 2 - Get content remotely
# Subtest: Remote source with blank node
# Subtest: RDF Fixture object ok
ok 1 - instantiate RDF Fixture object
ok 2 - RDF Fixture object is blessed
ok 3 - 'RDF Fixture object' isa 'Test::FITesque::RDF'
ok 4 - 'RDF Fixture object' isa 'Moo::Object'
ok 5 - Test::FITesque::RDF->can(...)
1..5
ok 1 - RDF Fixture object ok
ok 2 - Blank node is unsupported
1..2
ok 3 - Remote source with blank node
ok 4 - no (unexpected) warnings (via done_testing)
1..4
ok
t/unit-list.t ..............
ok 1 - use Test::FITesque::RDF;
ok 2 - Compare the data structures
1..2
ok
t/unit-multi-http.t ........
ok 1 - use Test::FITesque::RDF;
ok 2 - Check basic structure
ok 3 - Origin header found
ok 4 - ACAO header found
ok 5 - CORS echos origin
1..5
ok
t/unit-multi-vocab.t .......
ok 1 - use Test::FITesque::RDF;
ok 2
1..2
ok
t/unit-multi.t .............
ok 1 - use Test::FITesque::RDF;
ok 2 - Compare the data structures
1..2
ok
t/unit-relative.t ..........
# Subtest: $t ok
ok 1 - instantiate $t
ok 2 - $t is blessed
ok 3 - '$t' isa 'Test::FITesque::RDF'
ok 4 - '$t' isa 'Moo::Object'
ok 5 - Test::FITesque::RDF->can(...)
1..5
ok 1 - $t ok
ok 2
ok 3 - no (unexpected) warnings (via done_testing)
1..3
ok
t/unit-simple.t ............
# Subtest: $t ok
ok 1 - instantiate $t
ok 2 - $t is blessed
ok 3 - '$t' isa 'Test::FITesque::RDF'
ok 4 - '$t' isa 'Moo::Object'
ok 5 - Test::FITesque::RDF->can(...)
1..5
ok 1 - $t ok
ok 2
ok 3 - no (unexpected) warnings (via done_testing)
1..3
ok
Test Summary Report
-------------------
t/integration-basic.t (Wstat: 256 (exited 1) Tests: 7 Failed: 1)
Failed test: 7
Non-zero exit status: 1
Files=13, Tests=61, 8 wallclock secs ( 0.04 usr 0.01 sys + 7.13 cusr 1.00
csys = 8.18 CPU)
Result: FAIL
Failed 1/13 test programs. 1/61 subtests failed.
make[2]: *** [Makefile:864: test_dynamic] Error 255
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_test: error: make -j2 test TEST_VERBOSE=1 returned exit code 2
make[1]: *** [debian/rules:8: override_dh_auto_test] Error 25
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:4: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--------------------------------------------------------------------------------
The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:
https://people.debian.org/~sanvila/build-logs/202501/
About the archive rebuild: The build was made on virtual machines from AWS,
using sbuild and a reduced chroot with only build-essential packages.
If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.
If this is really a bug in one of the build-depends, please use
reassign and add an affects on src:libtest-fitesque-rdf-perl, so that this is
still
visible in the BTS web page for this package.
Thanks.
