public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: frysk@sourceware.org
Cc: Andrew Cagney <cagney@sourceware.org>
Subject: Re: [SCM]  master: Add INFO log-level; use warning level instead 	of System.out.println.
Date: Mon, 17 Mar 2008 11:00:00 -0000	[thread overview]
Message-ID: <1205750862.7607.35.camel@localhost.localdomain> (raw)
In-Reply-To: <1205492803.27548.33.camel@dijkstra.wildebeest.org>

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

  reply	other threads:[~2008-03-17 11:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080313192850.25428.qmail@sourceware.org>
2008-03-14 11:07 ` Mark Wielaard
2008-03-17 11:00   ` Mark Wielaard [this message]
2008-03-26 11:12     ` Mark Wielaard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1205750862.7607.35.camel@localhost.localdomain \
    --to=mark@klomp.org \
    --cc=cagney@sourceware.org \
    --cc=frysk@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).