[pkg-php-pear] Bug#766466: php-guzzle: ftbfs and (sometimes) after built attempt in pbuilder, nodejs still runs server.js

[Holger Levsen]

Hi David,

On Donnerstag, 23. Oktober 2014, David Prévot wrote:
> Thanks for your work on reproducible builds, and for following up on
> individual issues like this one.

thanks :)
 
> My guess is it’s due to a previous “Segmentation fault” failed build:
> AFAICT, a proper tear down is made at the end of the tests, even if some
> fail (and the segfault you’re having prevents to execute this tear
> down).

ok, i've just rescheduled the package on jenkins.d.n, the result should be 
available in 5-15m or so. 

Once that has happened 
https://jenkins.debian.net/userContent/rb-pkg/php-guzzle.html will not show 
"php-guzzle 3.9.2+dfsg-4 at 2014-10-23 05:06" anymore... :)

(and the rbuild.log linked is the pbuilder log plus some framing output)
 
> > <h1>ERROR</h1> <h2>The requested URL could not be retrieved</h2> </div>
> > <hr>  <div id="content"> <p>The following error was encountered while
> > trying to retrieve the URL: <a
> > href="http://127.0.0.1:123/">http://127.0.0.1:123/</a></p>  <blockquote
> > id="error"> <p><b>Access Denied.</b></p> </blockquote>
> 
> Do you have a process actually listening locally on port 123? Some tests
> are using http://127.0.0.1:123 to test a failure to connect…

not a process listening, but at least locally my firewall will not allow that. 
on jenkins.d.n there is neither an ntpd running nor such a firewall, but of 
course other builds could have used port 123...
 
> > In a normal sid it fails like this:
> > +Via: 1.1 tinyproxy (tinyproxy/1.8.3)
> Heh, I through this error was due to tinyproxy, but after installing it
> locally, I still don’t manage to reproduce your test issues. Do you have
> a specific setup for it? Do you still reproduce the test issues once
> tinyproxy removed (or at least stopped)?

then outside network access will not work anymore... do you tests really need 
internet access or "just" local net?

> Not sure how to address the problem: the build still runs fine for me,
> either on my machine, or in a proper minimal chroot via pbuilder or
> sbuild. php-guzzle did not FTBFS in the recent full archive rebuild
> either.

let me do a normal pbuilder build on jenkins.d.n....

fails again. see attached :-)

> In order to at least workaround the issue for the reproducible builds,
> can you simply deactivate the tests (add nocheck to DEB_BUILD_OPTIONS)
> for this package?

how would you enable such a workaround? that's not a good idea, we want 
packages to always build reproducibly! :)


cheers,
	Holger
-------------- next part --------------
A non-text attachment was scrubbed...
Name: php-guzzle_3.9.2+dfsg-4.log
Type: text/x-log
Size: 165239 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-php-pear/attachments/20141023/750d00be/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 828 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-php-pear/attachments/20141023/750d00be/attachment-0001.sig>