At the moment I don't have an idea, what's going wrong in the Ubuntu 
autopkgtest here.
But it looks as privoxy does not listen on 8119 as expected but fails and dies 
(the message, that privoxy cannot be killed because there is no such process in 
line 61 of privoxy-regression-test also leads to this conclusion).

Sadly we currently have too less information here.  I just committed two
patches to the Debian repository
https://salsa.debian.org/debian/privoxy, that should extend logging of
privoxy testsuite and preserve the logfiles into artifacts.

Maybe this helps to track this issue down.  I plan to release this as
privoxy 3.0.34-4 when the 64bit time_t migration is completed, so this
may take some weeks.

In the meantime you can try out the attached patch.

** Patch added: "artifacts-log.patch"
   
https://bugs.launchpad.net/ubuntu/+source/privoxy/+bug/2059344/+attachment/5760244/+files/artifacts-log.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059344

Title:
  3.0.34-3ubuntu1 autopkgtest failure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/privoxy/+bug/2059344/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to