Your message dated Wed, 23 Mar 2022 13:11:34 +0100
with message-id <ba431566-bc63-04f5-e42a-094a30122...@debian.org>
and subject line Re: os-autoinst: FTBFS: test failure
has caused the Debian Bug report #1004818,
regarding os-autoinst: FTBFS: test failure
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1004818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004818
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: os-autoinst
Version: 4.6.1632799442.f77d4e1-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs

os-autoinst FTBFS in unstable:

    Start 3: test-perl-testsuite

3: Test command: /<<PKGBUILDDIR>>/tools/invoke-tests "--prove-tool" 
"/usr/bin/prove" "--make-tool" "/usr/bin/ninja" "--build-directory" 
"/<<PKGBUILDDIR>>/build"
3: Test timeout computed to be: 10000000
3: [12:23:12] ./00-compile-check-all.t ................. ok    30351 ms ( 0.05 
usr  0.00 sys + 26.74 cusr  3.13 csys = 29.92 CPU)
3: [12:23:13] ./01-test_needle.t ....................... ok     1246 ms ( 0.02 
usr  0.00 sys +  1.28 cusr  0.11 csys =  1.41 CPU)
3: [12:23:14] ./02-test_ocr.t .......................... ok      707 ms ( 0.00 
usr  0.00 sys +  0.73 cusr  0.09 csys =  0.82 CPU)
3: [12:23:14] ./03-testapi.t ........................... ok      486 ms ( 0.01 
usr  0.00 sys +  0.46 cusr  0.02 csys =  0.49 CPU)
3: [12:23:15] ./04-check_vars_docu.t ................... ok       77 ms ( 0.00 
usr  0.00 sys +  0.07 cusr  0.01 csys =  0.08 CPU)
3: [12:23:15] ./04-testapi-python.t .................... ok      362 ms ( 0.00 
usr  0.00 sys +  0.33 cusr  0.02 csys =  0.35 CPU)
3: [12:23:15] ./05-distribution.t ...................... ok      276 ms ( 0.00 
usr  0.00 sys +  0.26 cusr  0.02 csys =  0.28 CPU)
3: Useless use of a constant ("can load python test module at a"...) in void 
context at ./08-autotest.t line 342.
3: [2022-02-01T12:23:16.070 UTC] [debug] scheduling test tests/test.py
3: [12:23:16] ./08-autotest.t .......................... ok      377 ms ( 
0.01 usr  0.00 sys +  0.35 cusr  0.03 csys =  0.39 CPU)
3: [12:23:17] ./10-terminal.t .......................... ok     1418 ms ( 0.01 
usr  0.00 sys +  0.28 cusr  0.08 csys =  0.37 CPU)
3: [12:23:18] ./10-test-image-conversion-benchmark.t ... ok     1435 ms ( 0.01 
usr  0.00 sys +  1.37 cusr  0.06 csys =  1.44 CPU)
3: 
[12:23:19]
 ./10-virtio_terminal.t ................... ok      379 ms ( 0.00 usr  0.00 sys 
+  0.32 cusr  0.06 csys =  0.38 CPU)
3: [12:23:19] ./11-image-ppm.t ......................... ok      309 ms ( 0.00 
usr  0.00 sys +  0.29 cusr  0.03 csys =  0.32 CPU)
3: [12:23:19] ./12-bmwqemu.t ........................... ok      248 ms ( 0.00 
usr  0.00 sys +  0.23 cusr  0.01 csys =  0.24 CPU)
3: [12:23:20] ./15-logging.t ........................... ok      234 ms ( 0.00 
usr  0.00 sys +  0.22 cusr  0.02 csys =  0.24 CPU)
3: [12:23:20] ./16-send_with_fd.t ...................... ok      320 ms ( 0.00 
usr  0.00 sys +  0.27 cusr  0.05 csys =  0.32 CPU)
3: [12:23:20] ./17-basetest.t .......................... ok      298 ms ( 0.00 
usr  0.00 sys +  0.28 cusr  0.03 csys =  0.31 CPU)
3: [12:23:22] ./18-qemu.t .............................. ok     1382 ms ( 0.01 
usr  0.00 sys +  0.29 cusr  0.09 csys =  0.39 CPU)
3: [12:23:22] ./19-isotovideo-command-processing.t ..... ok      298 ms ( 0.00 
usr  0.00 sys +  0.27 cusr  0.03 csys =  0.30 CPU)
3: [12:23:22] ./20-openqa-benchmark-stopwatch-utils.t .. ok      117 ms ( 0.00 
usr  0.00 sys +  0.09 cusr  0.03 csys =  0.12 CPU)
3: 
3: #   Failed test 'no (unexpected) warnings (via done_testing)'
3: #   at ./21-needle-downloader.t line 126.
3: # Got the following unexpected warnings:
3: #   1: Mojo::Reactor::Poll: Timer failed: Label not found for "last 
T2_SUBTEST_WRAPPER" at /usr/share/perl/5.32/Test2/Hub/Subtest.pm line 67.
3: # Looks like you failed 1 test of 5.
3: [12:23:40] ./21-needle-downloader.t ................. 
3: Dubious, test returned 1 (wstat 256, 0x100)
3: Failed 1/5 subtests 
3: [12:23:40] ./22-svirt.t ............................. ok      457 ms ( 0.01 
usr  0.01 sys +  0.41 cusr  0.06 csys =  0.49 CPU)
3: [12:23:41] ./23-baseclass.t ......................... ok      292 ms ( 0.00 
usr  0.00 sys +  0.23 cusr  0.06 csys =  0.29 CPU)
3: [12:23:41] ./24-myjsonrpc-debug.t ................... ok      231 ms ( 0.01 
usr  0.00 sys +  0.22 cusr  0.01 csys =  0.24 CPU)
3: [12:23:41] ./24-myjsonrpc.t ......................... ok      233 ms ( 0.00 
usr  0.00 sys +  0.23 cusr  0.01 csys =  0.24 CPU)
3: [12:23:41] ./25-spvm.t .............................. ok      297 ms ( 0.00 
usr  0.00 sys +  0.27 cusr  0.02 csys =  0.29 CPU)
3: [12:23:41] ./26-serial_screen.t ..................... ok      117 ms ( 0.00 
usr  0.00 sys +  0.09 cusr  0.03 csys =  0.12 CPU)
3: [12:23:42] ./26-ssh_screen.t ........................ ok      131 ms ( 0.00 
usr  0.00 sys +  0.12 cusr  0.01 csys =  0.13 CPU)
3: [12:23:42] ./28-signalblocker.t ..................... ok      447 ms ( 0.00 
usr  0.00 sys +  0.32 cusr  0.14 csys =  0.46 CPU)
3: [12:23:42] ./29-backend-generalhw.t ................. ok      369 ms ( 0.00 
usr  0.00 sys +  0.29 cusr  0.03 csys =  0.32 CPU)
3: [12:23:43] ./29-backend-ipmi.t ...................... ok      388 ms ( 0.01 
usr  0.00 sys +  0.35 cusr  0.04 csys =  0.40 CPU)
3: [12:23:43] ./29-backend-s390x.t ..................... ok      288 ms ( 0.00 
usr  0.00 sys +  0.26 cusr  0.03 csys =  0.29 CPU)
3: [12:24:02] ./30-mmapi.t ............................. ok    19112 ms ( 0.01 
usr  0.01 sys +  0.45 cusr  0.04 csys =  0.51 CPU)
3: [12:24:04] ./31-sshSerial.t ......................... ok     1446 ms ( 0.00 
usr  0.00 sys +  0.26 cusr  0.04 csys =  0.30 CPU)
3: [12:24:04] ./32-console_proxy.t ..................... ok      312 ms ( 0.00 
usr  0.00 sys +  0.29 cusr  0.02 csys =  0.31 CPU)
3: 
[12:24:04]
 ./33-vagrant.t ........................... ok      334 ms ( 0.01 usr  0.00 sys 
+  0.31 cusr  0.02 csys =  0.34 CPU)
3: [12:24:05] ./34-git.t ............................... ok      432 ms ( 0.00 
usr  0.00 sys +  0.33 cusr  0.11 csys =  0.44 CPU)
3: [12:24:05]
3: 
3: Test Summary Report
3: -------------------
3: ./21-needle-downloader.t               (Wstat: 256 Tests: 5 Failed: 1)
3:   Failed test:  5
3:   Non-zero exit status: 1
3: Files=36, Tests=949, 83 wallclock secs ( 0.23 usr  0.04 sys + 38.81 cusr  
4.64 csys = 43.72 CPU)
3: Result: FAIL
3/3 Test #3: test-perl-testsuite ..............***Failed   83.09 sec

The following tests passed:
        test-installed-files
        test-doc-testapi-spellchecking

67% tests passed, 1 tests failed out of 3

Total Test time (real) =  83.34 sec

The following tests FAILED:
          3 - test-perl-testsuite (Failed)
Errors while running CTest
Output from these tests are in: 
/<<PKGBUILDDIR>>/build/Testing/Temporary/LastTest.log
Use "--rerun-failed --output-on-failure" to re-run the failed cases verbosely.
FAILED: CMakeFiles/check-pkg-build 
/<<PKGBUILDDIR>>/build/CMakeFiles/check-pkg-build 
cd /<<PKGBUILDDIR>>/build && /usr/bin/ctest -V -E test-local-.*

Cheers
-- 
Sebastian Ramacher

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message ---
Version: 4.6.1632799442.f77d4e1-1

I verified that version 4.6.1632799442.f77d4e1-1 doesn't FTBFS anymore,
as already reported by Roland, so I'm marking this bug as Done.

--- End Message ---

Reply via email to