Curt, before I re-enable the FileWatchdog test case, can you try it on your
machine? I cleaned it up some, but looking at the code I'm not sure how it
was still printing the debug message. It explicitly checks the level on the
logger is INFO before printing any messages. But try it now.
thanks,
-Mark
----- Original Message -----
From: "Curt Arnold" <[EMAIL PROTECTED]>
To: "Log4J Developers List" <log4j-dev@logging.apache.org>
Sent: Thursday, January 19, 2006 8:46 PM
Subject: Re: svn commit: r370726 - in
/logging/log4j/trunk/tests/witness/watchdog: watchdog.FileWatchdog.test1.txt
watchdog.FileWatchdog.test2.txt
I don't think this fixes the problem since I was seeing that sometimes the
generated files contained DEBUG and other times it didn't. My Mac build
will now fails with the new witness files since the generated files
contain the DEBUG line.
The previous Gump failures show inconsistent generated files. In
http://marc.theaimsgroup.com/?l=log4j-dev&m=113766882315669&w=2, DEBUG is
missing in the generated files but present in the witness. In
http://marc.theaimsgroup.com/?l=log4j-dev&m=113761865108336&w=2, DEBUG is
present in the generated files but missing in the witness.
My supposition is there is some delay in these tests that is sometime
sufficient for a watchdog action to be completed, but sometime isn't.
On Jan 19, 2006, at 10:18 PM, [EMAIL PROTECTED] wrote:
Author: mwomack
Date: Thu Jan 19 20:18:47 2006
New Revision: 370726
URL: http://svn.apache.org/viewcvs?rev=370726&view=rev
Log:
Restoring file watchdog witness files
Modified:
logging/log4j/trunk/tests/witness/watchdog/
watchdog.FileWatchdog.test1.txt
logging/log4j/trunk/tests/witness/watchdog/
watchdog.FileWatchdog.test2.txt
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
