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

[Mark Wielaard <mark@klomp.org>]

Hi Andrew,

On Thu, 2008-03-13 at 19:28 +0000, cagney@sourceware.org wrote:
> commit 2404d069602dc2b49eb5355039d2ed59c0e1cfb7
> Author: Andrew Cagney <cagney@redhat.com>
> Date:   Thu Mar 13 15:27:22 2008 -0400
>  [...]    
>     frysk-sys/frysk/rsl/ChangeLog
>     2008-03-13  Andrew Cagney  <cagney@redhat.com>
>     
>     	* Log.java (prefixTimeAndPid()): For WARNING/INFO, include level.
>     	* LogFactory.java (info(Class)): New.
>     	(info(String)): New.
>     	* Level.mkenum (INFO): New; make default.

This seems to be causing:

testLevelComparison(frysk.rsl.TestLog)junit.framework.AssertionFailedError: DEFAULT expected:<Level_INFO> but was:<Level_WARNING>
   at frysk.rsl.TestLog.testLevelComparison(TestRunner)
   at frysk.junit.Runner.runCases(TestRunner)
   at frysk.junit.Runner.runTestCases(TestRunner)
   at TestRunner.main(TestRunner)

Also filed as bug #5937.

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.

Thanks,

Mark