From: John W. L. <Joh...@sa...> - 2012-11-15 15:22:52
|
The logging level during instrumentation is determined by the log4j settings. My bet is that you have a log4j.properties file in the classpath during instrumentation. It is probably on the classpath before the cobertura.jar since the cobertura.jar also has a log4j.properties file. It is also possible that someone may have modified the log4j.properties file that is in your cobertura.jar. -----Original Message----- From: KARR, DAVID [mailto:dk...@at...] Sent: Tuesday, November 13, 2012 10:06 AM To: Matthieu Moy Cc: cob...@li... Subject: Re: [Cobertura-devel] How to turn off Cobertura debug output > -----Original Message----- > From: Matthieu Moy [mailto:Mat...@gr...] > Sent: Tuesday, November 13, 2012 12:33 AM > To: KARR, DAVID > Cc: cob...@li... > Subject: Re: [Cobertura-devel] How to turn off Cobertura debug output > > "KARR, DAVID" <dk...@at...> writes: > > > I recently set up some Ant targets to run Cobertura with our unit > > tests. I got it to work, but I noticed today that Cobertura suddenly > > decided to emit its debug output, > > You mean those > > Flushing results... > Flushing results done > Cobertura: Loaded information on 167 classes. > Cobertura: Saved information on 167 classes. > > ? Actually, those are annoying, and I'd like to reduce them, but yesterday the volume increased a hundredfold, with lines like this for every single file being processed: 2012-11-12 15:52:30,753 DEBUG [net.sourceforge.cobertura.instrument.Main] [addInstrumentationToSingleClass] [Thread:main] - [Instrumenting class ... 2012-11-12 15:54:43,351 DEBUG [net.sourceforge.cobertura.util.FileFinder] [getFileForSource] [Thread:main] - [Searching for file, name=[... 2012-11-12 15:55:05,656 DEBUG [net.sourceforge.cobertura.reporting.xml.XMLReport] [dumpClass] [Thread:main] - [Dumping class ... 2012-11-12 15:55:44,245 DEBUG [net.sourceforge.cobertura.util.FileFinder] [getFileForSource] [Thread:main] - [Searching for file, name=[... I got a direct reply on this from someone on the project who said this is a known problem, and they're working on a fix. > > which produces a great deal of output. I didn't intentionally turn > > this on, and I don't see what might be turning this on. I'm just > using > > the "cobertura-instrument" task without any special flags. What > > might be doing this? > > The cobertura-instrumented classes call the cobertura runtime that > produces these outputs. I also have problem with them, and proposed a > patch to allow the user to disable it: > > > http://sourceforge.net/tracker/?func=detail&aid=3577330&group_id=13055 > 8 > &atid=720017 > > Unfortunately, it seems the patch didn't receive any attention. > > Do I need to do anything to have the patch applied? What is the github > migration status? Shall I submit a merge request anywhere? > > Thanks, > > -- > Matthieu Moy > http://www-verimag.imag.fr/~moy/ ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ Cobertura-devel mailing list Cob...@li... https://lists.sourceforge.net/lists/listinfo/cobertura-devel |