Hi Holger, Thanks for your work on reproducible builds, and for following up on individual issues like this one.
On Thu, Oct 23, 2014 at 12:42:43PM +0200, Holger Levsen wrote: > Package: php-guzzle > I noticed this process long after the build: > > 48059 ? SNl 0:00 nodejs > /tmp/buildd/php-guzzle-3.9.2+dfsg/tests/Guzzle/Tests/Http/server.js 8124 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). > the pbuilder build attempt itself failed like this: > <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… > .............[31;1mE[0m............................................... 427 > / 1531 ( 27%) > .......................................[41;37mF[0m[41;37mF[0m.debian/rules:14: > recipe for target 'override_dh_auto_test' failed > make[1]: *** [override_dh_auto_test] Segmentation fault That seems worse than a failing test (segfault around 30% of running tests), not sure where this one comes from right now. > Then I've tried to manually confirm that this also happens in a normal sid > build environment, but could "only" confirm the FTBFS problem, not the > hanging process. Since the testsuite runs fully, the proper tear down happens, so it seems to confirm the dandling process was due to the segfault. > In a normal sid it fails like this: > --- Expected > +++ Actual > @@ @@ > 'HTTP/1.1 200 OK > +Via: 1.1 tinyproxy (tinyproxy/1.8.3) > Content-Length: 5 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)? 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. 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? Regards David
signature.asc
Description: Digital signature
