public inbox for
 help / color / mirror / Atom feed
From: Mark Wielaard <>
Cc: Andrew Cagney <>
Subject: Re: [SCM]  master: Add INFO log-level; use warning level instead 	of System.out.println.
Date: Fri, 14 Mar 2008 11:07:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Andrew,

On Thu, 2008-03-13 at 19:28 +0000, wrote:
> commit 2404d069602dc2b49eb5355039d2ed59c0e1cfb7
> Author: Andrew Cagney <>
> Date:   Thu Mar 13 15:27:22 2008 -0400
>  [...]    
>     frysk-sys/frysk/rsl/ChangeLog
>     2008-03-13  Andrew Cagney  <>
>     	* (prefixTimeAndPid()): For WARNING/INFO, include level.
>     	* (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( {,pid=18639,tid=18640,state=detached} in state "detached" did not handle handleStoppedEvent SIGSTOP(19)
   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.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.



       reply	other threads:[~2008-03-14 11:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2008-03-14 11:07 ` Mark Wielaard [this message]
2008-03-17 11:00   ` Mark Wielaard
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:

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

  git send-email \ \ \ \ \

* 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).