← Back to team overview

dolfin team mailing list archive

Silencing debug output with nosetest

 

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


Follow ups