* Re: [SCM] master: Add INFO log-level; use warning level instead of System.out.println. [not found] <20080313192850.25428.qmail@sourceware.org> @ 2008-03-14 11:07 ` Mark Wielaard 2008-03-17 11:00 ` Mark Wielaard 0 siblings, 1 reply; 3+ messages in thread From: Mark Wielaard @ 2008-03-14 11:07 UTC (permalink / raw) To: frysk; +Cc: Andrew Cagney 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 ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [SCM] master: Add INFO log-level; use warning level instead of System.out.println. 2008-03-14 11:07 ` [SCM] master: Add INFO log-level; use warning level instead of System.out.println Mark Wielaard @ 2008-03-17 11:00 ` Mark Wielaard 2008-03-26 11:12 ` Mark Wielaard 0 siblings, 1 reply; 3+ messages in thread From: Mark Wielaard @ 2008-03-17 11:00 UTC (permalink / raw) To: frysk; +Cc: Andrew Cagney Hi Andrew, On Fri, 2008-03-14 at 12:06 +0100, Mark Wielaard wrote: > 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. You seem to have fixed this with: commit 963501ea208d03400e55c48ff8e28053f6b8e5b7 Author: Andrew Cagney <cagney@redhat.com> Date: Fri Mar 14 16:07:14 2008 -0400 Separate out/fix DEFAULT test. frysk-sys/frysk/rsl/ChangeLog 2008-03-14 Andrew Cagney <cagney@redhat.com> I closed the bug for you. > 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? Thanks, Mark ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [SCM] master: Add INFO log-level; use warning level instead of System.out.println. 2008-03-17 11:00 ` Mark Wielaard @ 2008-03-26 11:12 ` Mark Wielaard 0 siblings, 0 replies; 3+ messages in thread From: Mark Wielaard @ 2008-03-26 11:12 UTC (permalink / raw) To: frysk; +Cc: Andrew Cagney 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 ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2008-03-26 11:12 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <20080313192850.25428.qmail@sourceware.org>
2008-03-14 11:07 ` [SCM] master: Add INFO log-level; use warning level instead of System.out.println Mark Wielaard
2008-03-17 11:00 ` Mark Wielaard
2008-03-26 11:12 ` Mark Wielaard
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).