On Thu, Apr 14, 2016 at 07:48:47AM +0200, Stefan Fritsch wrote: > reassign 820824 apache2
> On Tuesday 12 April 2016 23:04:42, Niko Tyni wrote: > > Looking at the CI results at > > > > https://ci.debian.net/packages/liba/libapache2-mod-perl2/unstable/a > > md64/ this started happening between 2016-04-09 and 2016-04-10, > > probably with the apache2 2.4.18 -> 2.4.20 upgrade. > > > > I can get this to happen with just > > # ./t/TEST -verbose -httpd_conf $(pwd)/debian/apache2.conf > > t/protocol/pseudo_http.t > > > > and I see the Apache server process dies with SIGSEGV. Backtrace > > below. > > > > Cc'ing the Apache maintainers, seems to be a regression there? > > Seems likely. Reassigning to keep 2.4.20-1 from migrating to testing > for now. This is also https://mail-archives.apache.org/mod_mbox/httpd-dev/201604.mbox/%3CCACsi250G0azcA-XyJHGLxacpDEg_ezJ=taus31pyb7g_8-x...@mail.gmail.com%3E which says that while apache2 shouldn't crash, the mod_perl2 test is buggy and should be fixed. Unfortunately mod_perl2 upstream is very quiet these days, so nothing has happened so far on this front. I intend to disable the test in libapache2-mod-perl2 for now until a better solution is found. Do you want to track the apache2 crash with this bug, or should we reassign it back? Thanks, -- Niko Tyni nt...@debian.org
