[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: kern/47563: test cases do not timeout and hang
The following reply was made to PR kern/47563; it has been noted by GNATS.
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>
> The following reply was made to PR kern/47563; it has been noted by =
> From: Martin Husemann <martin%duskware.de@localhost>
> To: gnats-bugs%NetBSD.org@localhost
> Cc: Antti Kantee <pooka%NetBSD.org@localhost>, Julio Merino
> 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
> 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 =
>> on that, ktrace shows it dropping out of poll() regularily.
> 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?=
Main Index |
Thread Index |