Your message dated Sun, 17 Apr 2016 11:45:50 +0100
with message-id 
<1460889950.1822265.581120721.41bee...@webmail.messagingengine.com>
and subject line Re: Bug#821233: perlbal: FTBFS: Unable to start socket: 
Address already in use
has caused the Debian Bug report #821233,
regarding perlbal: FTBFS: Unable to start socket: Address already in use
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.)


-- 
821233: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821233
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: perlbal
Version: 1.80-3
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

perlbal fails to build from source in unstable/amd64:

  [..]

  ok 5 - single GET okay
  ok 6 - got signal
  ok 7 - 200 to POST w/ pipelined GET after
  ok 8 - didn't get signal from GET after POST
  ok 9 - 200 to POST w/ pipelined GET after
  ok 10 - didn't get signal from GET after POST
  ok 11 - single GET okay
  ok 12 - pipelined when not expecting it
  ok
  Didn't get 200 OK: GET /reqdecr,status HTTP/1.0
  Unable to start socket: Address already in use
  # Looks like your test exited with 29 before it could output anything.
  t/32-selector.t .......... 
  1..38
  Dubious, test returned 29 (wstat 7424, 0x1d00)
  Failed 38/38 subtests 
  t/35-reproxy.t ........... 
  ok 1 - web servers started
  beginning run
  ok 2 - perlbal started
  ok 3 - status response ok
  ok 4 - file good via disk
  ok 5 - file good via network
  ok 6 - reproxy file
  ok 7 - ... and keep-alives are on
  ok 8 - reproxy file
  ok 9 - ... and keep-alives are on
  ok 10 - 2 on same conn
  ok 11 - reproxy URL
  ok 12 - response code is 200
  ok 13 - ... and keep-alives are on
  ok 14 - reproxy URL
  ok 15 - response code is 200
  ok 16 - ... and keep-alives are on
  ok 17 - 4 on same conn
  ok 18 - reproxy URL
  ok 19 - 204 response code is 200
  ok 20 - ... and keep-alives are on
  ok 21 - reproxy URL
  ok 22 - 204 response code is 200
  ok 23 - ... and keep-alives are on
  ok 24 - Prior to first hit, counter should be zero.
  ok 25 - reproxy with cache: One
  ok 26 - ... and keep-alives are on
  ok 27 - Got a response
  ok 28 - reproxy with cache ims, got 304 correctly: One
  ok 29 - ... and keep-alives are on
  ok 30 - First hit to populate the cache.
  ok 31 - reproxy with cache: Two
  ok 32 - ... and keep-alives are on
  ok 33 - Got a response
  ok 34 - reproxy with cache ims, got 304 correctly: Two
  ok 35 - ... and keep-alives are on
  ok 36 - Second hit should be cached.
  ok 37 - Prior to third hit, counter should still be 1.
  ok 38 - reproxy with cache: Three
  ok 39 - ... and keep-alives are on
  ok 40 - Got a response
  ok 41 - reproxy with cache ims, got 304 correctly: Three
  ok 42 - ... and keep-alives are on
  ok 43 - Third hit isn't cached, now 2.
  ok 44 - reproxy with cache: Four
  ok 45 - ... and keep-alives are on
  ok 46 - Got a response
  ok 47 - reproxy with cache ims, got 304 correctly: Four
  ok 48 - ... and keep-alives are on
  ok 49 - Forth hit should be cached again, still 2.
  ok 50 - status ok
  ok 51 - status ok
  ok 52 - reproxy file
  ok 53 - ... and keep-alives are on
  ok 54 - reproxy URL
  ok 55 - response code is 200
  ok 56 - ... and keep-alives are on
  ok 57 - status ok
  ok 58 - reproxy URL
  ok 59 - response code is 200
  ok 60 - ... and keep-alives are on
  ok 61 - reproxy URL
  ok 62 - response code is 200
  ok 63 - ... and keep-alives are on
  ok 64 - reproxy file
  ok 65 - ... and keep-alives are on
  ok 66 - reproxy file
  ok 67 - ... and keep-alives are on
  ok 68 - reproxy URL
  ok 69 - response code is 200
  ok 70 - ... and keep-alives are on
  ok 71 - reproxy file
  ok 72 - ... and keep-alives are on
  ok 73 - status ok
  ok 74 - AIO mode none: 9 transitions
  ok 75 - status ok
  ok 76 - status ok
  ok 77 - reproxy file
  ok 78 - ... and keep-alives are on
  ok 79 - reproxy URL
  ok 80 - response code is 200
  ok 81 - ... and keep-alives are on
  ok 82 - status ok
  ok 83 - reproxy URL
  ok 84 - response code is 200
  ok 85 - ... and keep-alives are on
  ok 86 - reproxy URL
  ok 87 - response code is 200
  ok 88 - ... and keep-alives are on
  ok 89 - reproxy file
  ok 90 - ... and keep-alives are on
  ok 91 - reproxy file
  ok 92 - ... and keep-alives are on
  ok 93 - reproxy URL
  ok 94 - response code is 200
  ok 95 - ... and keep-alives are on
  ok 96 - reproxy file
  ok 97 - ... and keep-alives are on
  ok 98 - status ok
  ok 99 - AIO mode ioaio: 9 transitions
  ok 100 - reproxy URL w/ dead one first
  ok 101 - ... and keep-alives are on
  ok 102 - reproxy URL w/ 404 one first
  ok 103 - no response body when req method is HEAD
  1..103
  ok
  t/40-ranges.t ............ 
  1..35
  beginning run
  ok 1 - perlbal started
  ok 2 - backend port added
  ok 3 - status response ok
  ok 4 - file good via disk
  ok 5 - file good via network
  ok 6 - http/none: range bytes=0-6
  ok 7 - is partial
  ok 8 - http/none: range bytes=31-
  ok 9 - is partial
  ok 10 - http/none: can't satisify
  ok 11 - http/none: can't satisify
  ok 12 - http/ioaio: range bytes=0-6
  ok 13 - is partial
  ok 14 - http/ioaio: range bytes=31-
  ok 15 - is partial
  ok 16 - http/ioaio: can't satisify
  ok 17 - http/ioaio: can't satisify
  ok 18 - rp_file/none: range bytes=0-6
  ok 19 - is partial
  ok 20 - rp_file/none: range bytes=31-
  ok 21 - is partial
  ok 22 - rp_file/none: can't satisify
  ok 23 - rp_file/none: can't satisify
  ok 24 - rp_file/ioaio: range bytes=0-6
  ok 25 - is partial
  ok 26 - rp_file/ioaio: range bytes=31-
  ok 27 - is partial
  ok 28 - rp_file/ioaio: can't satisify
  ok 29 - rp_file/ioaio: can't satisify
  ok 30 - rp_url/-: range bytes=0-6
  ok 31 - is partial
  ok 32 - rp_url/-: range bytes=31-
  ok 33 - is partial
  ok 34 - rp_url/-: can't satisify
  ok 35 - rp_url/-: can't satisify
  ok
  t/50-plugins.t ........... 
  1..7
  ok 1 - require Perlbal::Plugin::Highpri;
  ok 2 - require Perlbal::Plugin::Palimg;
  ok 3 - require Perlbal::Plugin::Queues;
  ok 4 - require Perlbal::Plugin::Stats;
  ok 5 - require Perlbal::Plugin::Vhosts;
  ok 6 - require Perlbal::Plugin::MaxContentLength;
  ok 7 - require Perlbal::Plugin::Throttle;
  ok
  t/52-chunked-upload.t .... 
  ok 1 - webserver started
  beginning run
  ok 2 - perlbal started
  ok 3 - no files in buffer directory
  ok 4 - buffer_off: buffer file exists
  ok 5 - buffer_off: good response
  ok 6 - backend got right content-length
  ok 7 - buffer_off: no file
  ok 8 - Server still alive
  1..8
  ok
  t/60-child-httpd.t ....... skipped: Alpha feature; test skipped without 
$ENV{PERLBAL_TEST_ALPHA}
  t/75-plugin-include.t .... 
  1..8
  beginning run
  ok 1 - manage sock
  ok 2 - load include
  ok 3 - include single
  ok 4 - include multi
  ok 5 - error on nonexistent conf
  ok 6 - test_a loaded
  ok 7 - test_b loaded
  ok 8 - test_c loaded
  ok
  t/76-plugin-redirect.t ... 
  beginning run
  ok 1 - perlbal started
  ok 2 - Got a response
  ok 3 - Redirect has proper code
  ok 4 - Correct redirect response
  ok 5 - ... and keep-alives are on
  1..5
  ok
  t/77-plugin-throttle.t ... 
  1..2
  ok 1 # skip TODO
  ok 2 # skip TODO
  ok
  t/78-plugin-xffextras.t .. 
  1..4
  ok 1 - webserver started
  beginning run
  ok 2 - perlbal started
  ok 3 - Got an X-Forwarded-Port header that seems reasonable
  ok 4 - Got an X-Forwarded-Proto header that seems reasonable
  ok
  t/90-accesscontrol.t ..... 
  OK
  beginning run
  ok 1 - File was written properly
  ok 2 - UA object defined
  ok 3 - Manage context switch success
  ok 4 - Initial request succeeds
  ok 5 - ACCESS deny was set properly
  ok 6 - Denied
  ok 7 - Denied with XFF header
  ok 8 - Turning always trusted on
  ok 9 - Denied
  ok 10 - Allowed with XFF header
  ok 11 - Turning always trusted off again
  ok 12 - Turning trusted upstream proxies on for 127.0.0.1
  ok 13 - Denied
  ok 14 - Allowed with XFF header
  ok 15 - Turning trusted upstream proxies on for multiple netmasks
  ok 16 - Denied
  ok 17 - Allowed with XFF header
  ok 18 - Turning off observed IP
  ok 19 - Denied with XFF header
  1..19
  ok
  t/91-fields.t ............ 
  1..6
      # Subtest: before using Perlbal::Fields
      ok 1 - use Perlbal::CommandContext;
      ok 2 - use old library
      1..2
  ok 1 - before using Perlbal::Fields
  ok 2 - use Perlbal::Fields;
  ok 3 - run method
  ok 4 - 'can create object' isa 'Perlbal::Test::Fields'
  ok 5 - use Perlbal::CommandContext;
  ok 6 - 'can create object' isa 'Perlbal::CommandContext'
  ok
  t/99-benchmark-bool.t .... 
  1..5
  ok 1 - use Perlbal;
  ok 2 - use Perlbal::Service;
      # Subtest: module checking
      ok 1 - 'can create object from Perlbal::Service' isa 'Perlbal::Service'
      1..1
  ok 3 - module checking
      # Subtest: check sub integrity
      ok 1 - sub optimized
      ok 2 - sub hash
      1..2
  ok 4 - check sub integrity
      # Subtest: benchmark bool sub
      ok 1 - use Benchmark;
  Benchmark: timing 100000 iterations of hash, optimized, original, void...
        hash:  1 wallclock secs ( 0.08 usr +  0.00 sys =  0.08 CPU) @ 
1250000.00/s (n=100000)
              (warning: too few iterations for a reliable count)
   optimized:  0 wallclock secs ( 0.42 usr +  0.00 sys =  0.42 CPU) @ 
238095.24/s (n=100000)
    original:  0 wallclock secs ( 0.35 usr +  0.00 sys =  0.35 CPU) @ 
285714.29/s (n=100000)
              (warning: too few iterations for a reliable count)
        void:  0 wallclock secs ( 0.02 usr +  0.00 sys =  0.02 CPU) @ 
5000000.00/s (n=100000)
              (warning: too few iterations for a reliable count)
      1..1
  ok 5 - benchmark bool sub
  ok
  
  Test Summary Report
  -------------------
  t/32-selector.t        (Wstat: 7424 Tests: 0 Failed: 0)
    Non-zero exit status: 29
    Parse errors: Bad plan.  You planned 38 tests but ran 0.
  Files=24, Tests=514, 47 wallclock secs ( 0.21 usr  0.02 sys +  4.30 cusr  
0.30 csys =  4.83 CPU)
  Result: FAIL
  Failed 1/24 test programs. 0/514 subtests failed.
  Makefile:1158: recipe for target 'test_dynamic' failed
  make[2]: *** [test_dynamic] Error 255
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160416231458.oTasfXAQPd.perlbal/perlbal-1.80'
  dh_auto_test: make -j1 test TEST_VERBOSE=1 TEST_FILES=t/78-plugin-xffextras.t 
t/32-selector.t t/31-realworld.t t/13-server-tokens.t t/60-child-httpd.t 
t/17-webserver-concat.t t/35-reproxy.t t/99-benchmark-bool.t 
t/52-chunked-upload.t t/76-plugin-redirect.t t/15-webserver.t 
t/75-plugin-include.t t/32-pipelining.t t/22-chunked-put.t t/00-use.t 
t/40-ranges.t t/50-plugins.t t/30-reverseproxy.t t/77-plugin-throttle.t 
t/12-headers.t t/90-accesscontrol.t t/91-fields.t t/20-put.t t/10-testharness.t 
returned exit code 2
  debian/rules:9: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160416231458.oTasfXAQPd.perlbal/perlbal-1.80'
  debian/rules:6: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

-- 
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      la...@debian.org / chris-lamb.co.uk
       `-

Attachment: perlbal.1.80-3.unstable.amd64.log.txt.gz
Description: Binary data


--- End Message ---
--- Begin Message ---
> The tests pass for me, both during build and in autopkgtest.

The failed on yesterday's sid, but pass today. :)  Closing in Bcc..


Regards,

-- 
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      la...@debian.org / chris-lamb.co.uk
       `-

--- End Message ---

Reply via email to