Tags Tags

Bug#652331: libapache2-mod-perl2: FTBFS with apache2-mpm-event: tests hang

December 16th, 2011 - 04:50 am ET by Niko Tyni | Report spam
Help Create a new topic
Package: libapache2-mod-perl2
Version: 2.0.5-4
Severity: normal
X-Debbugs-Cc: apache2-mpm-event@packages.debian.org

When building libapache2-mod-perl2 with apache2-mpm-event instead of
apache2-mpm-worker, the test suite hangs. The test order is randomized
and the hanging test name isn't printed out when it hangs, but looking
at the process list reveals at least these (from different attempts):

t/error/runtime.t
t/hooks/startup.t
t/protocol/pseudo_http.t

Given this paragraph in the apache2-mpm-event description:

This MPM is experimental and less tested than the worker and prefork MPMs.

I think that just a Build-Conflicts declaration would be an appropriate
fix for this problem on the libapache2-mod-perl2 side.

Ideally the issues should of course be investigated properly and fixed
in the MPM code where applicable, but I'm not going to work on that.
Cc'ing the apache2 maintainers. Feel free to clone/reassign if you
want to track this.
Niko Tyni ntyni@debian.org



To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
email Follow the discussionReplies 1 replyReplies Make a reply

Similar topics

Replies

#1 Stefan Fritsch
December 18th, 2011 - 05:40 am ET | Report spam
On Friday 16 December 2011, Niko Tyni wrote:
Given this paragraph in the apache2-mpm-event description:

This MPM is experimental and less tested than the worker and
prefork MPMs.

I think that just a Build-Conflicts declaration would be an
appropriate fix for this problem on the libapache2-mod-perl2 side.



I agree. MPM event in 2.4 has lots of changes compared to 2.2 and is
no longer experimental. I would not waste time to debug that problem
in 2.2's MPM event.

Ideally the issues should of course be investigated properly and
fixed in the MPM code where applicable, but I'm not going to work
on that. Cc'ing the apache2 maintainers. Feel free to
clone/reassign if you want to track this.



Can you add a comment in your package, that this should be checked
again once 2.4 is released and in Debian? If it still happens then, a
but against apache2 would be appropriate.



To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact
email Follow the discussion Replies Reply to this message
Help Create a new topicReplies Make a reply
Search Make your own search