[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#614737: marked as done ([t/runtests] runtests doesn't fail if a a thread dies (e.g. because of die()))

Your message dated Mon, 05 Sep 2011 09:29:56 +0200
with message-id <4E647A74.3060108@thykier.net>
and subject line [t/runtests] runtests doesn't fail if a a thread dies (e.g. because of die())
has caused the Debian Bug report #614737,
regarding [t/runtests] runtests doesn't fail if a a thread dies (e.g. because of die())
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

614737: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614737
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: lintian
Version: 2.5.0~rc1


As subject says, t/runtests doesn't fail at the end even if a thread 
"terminates abnormally" (because of a call to die()).
I didn't fix it before uploading the rc1 because I've been hitting a bug in 
make (#614701) and even though I retried three times that bug hit me every 
single time, so in the end I just uploaded the package.

There are two ways to fix this bug: either by replacing the calls to fail(), or 
by making the for my $thr (threads->list()) loop actually check the return 
status of the thread and re-start it if it died.
The latter should really be done only after refactoring the code.

(I'm personally inclined to leaving this bug unfixed until the make bug is 
fixed. This bug doesn't affect tests that fail, only tests that fail to build.)

Raphael Geissert - Debian Developer
www.debian.org - get.debian.net

--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.2


This has been fixed; as I recall it was done in 2.5.2, but it might have
been a bit earlier.


--- End Message ---

Reply to: