Re: [SCM] master: Add INFO log-level; use warning level instead of System.out.println.

[Mark Wielaard <mark at klomp dot org>]

Hi Andrew,

On Mon, 2008-03-17 at 11:47 +0100, Mark Wielaard wrote:
> 
> > I am also seeing the following since yesterday:
> > 
> > 2) testBlockingFibonacciClone(frysk.proc.live.TestTaskObserverBlocked)java.lang.RuntimeException: {frysk.proc.live.LinuxPtraceTask@319faf55,pid=18639,tid=18640,state=detached} in state "detached" did not handle handleStoppedEvent SIGSTOP(19)
> >    at frysk.proc.live.State.unhandled(TestRunner)
> >    at frysk.proc.live.LinuxPtraceTaskState.handleStoppedEvent(TestRunner)
> >    at frysk.proc.live.LinuxPtraceTask.processStoppedEvent(TestRunner)
> >    at frysk.proc.live.LinuxWaitBuilder.stopped(TestRunner)
> >    at frysk.sys.Wait.wait(TestRunner)
> >    at frysk.sys.Wait.wait(TestRunner)
> >    at frysk.event.WaitEventLoop.block(TestRunner)
> >    at frysk.event.EventLoop.runEventLoop(TestRunner)
> >    at frysk.event.EventLoop.runPolling(TestRunner)
> >    at frysk.testbed.TestLib.assertRunUntilStop(TestRunner)
> >    at frysk.testbed.TestLib.assertRunUntilStop(TestRunner)
> >    at frysk.proc.live.TestTaskObserverBlocked.access$2(TestRunner)
> >    at frysk.proc.live.TestTaskObserverBlocked$BlockingFibonacci.<init>(TestRunner)
> >    at frysk.proc.live.TestTaskObserverBlocked$1$CloneFibonacci.<init>(TestRunner)
> >    at frysk.proc.live.TestTaskObserverBlocked.testBlockingFibonacciClone(TestRunner)
> >    at frysk.junit.Runner.runCases(TestRunner)
> >    at frysk.junit.Runner.runTestCases(TestRunner)
> >    at TestRunner.main(TestRunner)
> > 
> > Which I haven't tracked down to a specific commit yet. Bugzilla has it
> > as issue #3937. Might it be caused by one of your new StopEventLoop
> > patches from yesterday? If you could explain what those new patches do
> > that would be nice.
> 
> I don't see this issue anymore. Do you know what fixed it? And could you
> describe what your new StepEventLoop patches should accomplish?

Still not reappeared, so I closed the bug report. If you could comment
on whether your StepEventLoop patches might have been responsible for
the fix and what they are intended for that would be appreciated.

Thanks,

Mark