Control: tag -1 + confirmed On Tue, 14 Aug 2012 09:28:34 +0200, Lucas Nussbaum wrote:
> Source: fusioninventory-agent
> Version: 2.2.3-2
> Severity: serious
> Tags: wheezy sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20120814 qa-ftbfs
> Justification: FTBFS in wheezy on amd64
>
> Hi,
>
> During a rebuild of all packages in *wheezy*, your package failed to
> build on amd64.
>
> > Test Summary Report
> > -------------------
> > t/components/client/connection.t (Wstat: 768 Tests: 36 Failed: 3)
> > Failed tests: 14, 16, 18
> > Non-zero exit status: 3
> > t/components/client/ssl.t (Wstat: 256 Tests: 8 Failed: 1)
> > Failed test: 1
> > Non-zero exit status: 1
> > Files=94, Tests=947, 38 wallclock secs ( 0.50 usr 0.40 sys + 18.20 cusr
> > 6.13 csys = 25.23 CPU)
> > Result: FAIL
> > Failed 2/94 test programs. 4/947 subtests failed.
> > make[1]: *** [test_dynamic] Error 255
Interesting bug.
First, a ton of tests failed for me because I have http_proxy set in
my chroots. So far, so unusual.
Then I get different results because of PERL_LWP_SSL_VERIFY_HOSTNAME ...
After explicitly setting this to a true value (which is the default)
I get the same results as Lucas.
(With PERL_LWP_SSL_VERIFY_HOSTNAME=0 t/components/client/connection.t
passes and t/components/client/ssl.t fails in more/different subtests.)
> # Failed test 'trusted certificate, correct hostname: connection success'
> # at t/components/client/ssl.t line 78.
> # Looks like you failed 1 test of 8.
> t/components/client/ssl.t ................
expands with a bit debugging to
not ok 1 - trusted certificate, correct hostname: connection success
# Failed test 'trusted certificate, correct hostname: connection success'
# at t/components/client/ssl.t line 79.
$VAR1 = bless( {
'_content' => 'Can\'t connect to localhost:8080 (certificate
verify failed)
LWP::Protocol::https::Socket: SSL connect attempt failed with unknown error
error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify
failed at /usr/share/perl5/LWP/Protocol/http.pm line 51.
',
'_rc' => 500,
'_headers' => bless( {
'client-warning' => 'Internal response',
'client-date' => 'Tue, 28 Aug 2012
16:16:54 GMT',
'content-type' => 'text/plain'
}, 'HTTP::Headers' ),
'_msg' => 'Can\'t connect to localhost:8080 (certificate
verify failed)',
'_request' => bless( {
'_content' => '',
'_uri' => bless( do{\(my $o =
'https://localhost:8080/public')}, 'URI::https' ),
'_headers' => bless( {},
'HTTP::Headers' ),
'_method' => 'GET'
}, 'HTTP::Request' )
}, 'HTTP::Response' );
Hm, the upstream testsuite also doesn't look good:
http://www.cpantesters.org/distro/F/FusionInventory-Agent.html
Looking at the upstream diff between 2.2.3 and 2.2.5 is interesting.
Let's see how minimal we can get the patch ...
Hm, t/components/client/ssl.t still fails ...
Oh, one test cert (good.pem) is expired. How helpful!
Ok, I'm giving up. At least the SSL test keep failing.
Cheers,
gregor
--
.''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
: :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/
`. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
`- NP: U2: Sunday Bloody Sunday
signature.asc
Description: Digital signature
