A limited amount of googling yielded: nosetests --nologcapture
to prevent the logging from being captured. It also seems a log level setting feature has been requested before: http://code.google.com/p/python-nose/issues/detail?id=268 but is not currently implemented. Cheers Neilen On Mon, Jun 20, 2011 at 5:59 PM, Johan Hake <johan.h...@gmail.com> wrote: > I do not know nosetest, but it sounds like nosetest set the log level for the > root logger in the logging module, to DEBUG. If you find out how to alter the > log level to INFO, you might silence the extra output. > > Johan > > On Monday June 20 2011 08:46:02 Neilen Marais wrote: >> Hi, >> >> I find that when I get a failure when running dolfin code through >> nosetest (or unittest in general?) a _large_ amount of extra debug >> info generated by FFC, UFL, etc are included in the output that is >> captured by nosetest; stuff that I don't usually see. Is this on >> purpose? And more importantly, is there a way I can silence it? >> >> Thanks >> Neilen >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~dolfin >> Post to : dolfin@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~dolfin >> More help : https://help.launchpad.net/ListHelp > _______________________________________________ Mailing list: https://launchpad.net/~dolfin Post to : dolfin@lists.launchpad.net Unsubscribe : https://launchpad.net/~dolfin More help : https://help.launchpad.net/ListHelp
