Re: kern/47563: test cases do not timeout and hang

[julio%meroh.net@localhost]

The following reply was made to PR kern/47563; it has been noted by GNATS.

From: julio%meroh.net@localhost
To: martin%duskware.de@localhost
Cc: gnats-bugs%gnats.netbsd.org@localhost
Subject: Re: kern/47563: test cases do not timeout and hang
Date: Sat, 16 Feb 2013 16:29:12 -0500

 On Feb 16, 2013, at 15:55 , Martin Husemann <martin%duskware.de@localhost> 
wrote:
 
 > The following reply was made to PR kern/47563; it has been noted by =
 GNATS.
 >=20
 > From: Martin Husemann <martin%duskware.de@localhost>
 > To: gnats-bugs%NetBSD.org@localhost
 > Cc: Antti Kantee <pooka%NetBSD.org@localhost>, Julio Merino 
 > <jmmv%NetBSD.org@localhost>,
 >      rmind%NetBSD.org@localhost, gson%NetBSD.org@localhost
 > Subject: Re: kern/47563: test cases do not timeout and hang
 > Date: Sat, 16 Feb 2013 21:53:51 +0100
 >=20
 > On Sat, Feb 16, 2013 at 09:37:29PM +0100, Martin Husemann wrote:
 >> This leaves the open question why atf does not timeout - I have not =
 idea
 >> on that, ktrace shows it dropping out of poll() regularily.
 >=20
 > I verified that atf-run/timer.cpp marks the timer as fired and invokes
 > the callback.
 
 In all honesty, the code in atf-run that manages timeouts and muxes the =
 output of the tests is quite retarded.  I won't be surprised if there =
 are bugs lingering around... but it's hard to explain why such a bug =
 would only trigger in sparc64 if that's the case.
 
 What happens to the rump_allserver process?  Does it crash?  Maybe =
 attempting to reproduce its behavior under a different platform would =
 trigger the same atf-run bug, if any?=