Hi Holger, On Sat, Oct 25, 2014 at 11:57:34AM +0200, Holger Levsen wrote: > On Donnerstag, 23. Oktober 2014, David Prévot wrote:
> > Seems like the segfault is reproducible with the jenkins setup, but I
> > still don’t know what is causing it.
>
> yeah. Just tell me if you have something for me to try...
> > running phpunit
> > with the --debug switch should help pointing to the test actually
> > causing the segfault.
>
> how do I run that exactly?
Either by running directly, in the source package directory (with
patches applied):
phpunit --debug
or by adding “--debug” to phpunit in the override_dh_auto_test target of
debian/rules (so it will be used during the build).
> > A local server (with nodejs) is run for the purpose of these tests, and
> > some other tests use http://127.0.0.1:123/ to test failure to connect to
> > a server.
> > - in a normal sid (as pointed in your initial message), some tests are
> > failing, and some other error out.
Seems to be related to the proxy: if I run the test with http_proxy set
to use a local Squid, I manage to get failing tests (albeit without
segfault). I just uploaded 3.9.2+dfsg-5 that unsets http_proxy for
running the tests, please let me know if that’s enough for Jenkins (and
if the segfault vanished ;).
> yes, those are two bugs. I'll leave the cloning to you though. You have a
> better grasp whats happening.
Let’s see first if we’re able to kill two birds with one stone ;).
Regards
David
signature.asc
Description: Digital signature
