Re: newly-failing ftest cases

[christos%astron.com@localhost (Christos Zoulas)]

In article <20130401110156.GE10165%mail.duskware.de@localhost>,
Martin Husemann  <martin%duskware.de@localhost> wrote:
>On Mon, Apr 01, 2013 at 06:57:27AM -0400, Greg Troxel wrote:
>> 
>> Some time between 2013.03.27.19.23.28 and 2013.03.29.10.34.12, two
>> condwait and two bpf tests started failing.  It's hard to figure out
>> what happened there, because there were commits in between that caused
>> 84 tests to fail and broke the build.   But some of the commits touched
>> timeout stuff, so this doesn't seem like a false alarm.
>> 
>> 
>>
>http://releng.netbsd.org/b5reports/i386/build/2013.03.31.16.45.06/test.html#failed-tcs-summary
>
>This might be due to qemu timing issues, however, I just got an
>assertion failure in related code:
>
>panic: kernel diagnostic assertion "*timo > 0" failed: file
>"../../../../kern/subr_time.c", line 263

I made the test stricter. Are you getting 0?

christos