+1 It is hard to debug with lots logs messages. And if anybody is using them for development we can make those logs debug logs and hide them by default.
*From: *Robert Bradshaw <rober...@google.com> *Date: *Wed, May 8, 2019 at 3:01 PM *To: *dev +1 to making them significantly more compact in most cases. > > From: Pablo Estrada <pabl...@google.com> > Date: Wed, May 8, 2019 at 11:35 PM > To: dev > > > Hello all, > > Some tests in Python have the problem that when they fail, lots of > internal logging is dumped onto stdout, and we end up having to scroll way > up to find the actual stack trace for the failed test. This logging, as far > as i can tell, is dumping of fn api protos. > > > > Does anyone use these logs to look into the test failure? I would like > to find a way to make these more compact, or maybe just stop logging them > (people who need them can choose to log them in their local setup?). > > > > I lean towards making them more compact (by, for instance, writing > functions that log their information in a more compact fashion); but I > would like to hear thoughts from others. > > > > So thoughts? : ) > > -P. >
