Yes. We saw this came up in 2.1 release vote also. Justin thought that build stopped/stuck after the exception. With no information coming on console and if tests take time, people will assume that build is stuck. This would be still an issue after removing exception traces from console.
Thanks Amareshwari On Tue, May 12, 2015 at 2:21 PM, Jaideep Dhok <[email protected]> wrote: > Hi Yash, > Thanks for bringing that up, I believe Himanshu had also mentioned this > earlier. There are some places where we just print the stack trace and in > some places like the cube rewriter tests expected exceptions are always > printed. > > We have this and bunch of other tasks outlined in LENS-458. Please have a > look. If this is not there, please feel free to add to the backlog. > > Thanks, > Jaideep > > On Mon, May 11, 2015 at 7:50 PM, Yash Sharma <[email protected]> wrote: > > > Hi All, > > I would like to discuss if we should start cleaning our test cases. > > Currently the building the project with test cases explodes the console > > with Exception stack trace which looks very unfriendly and scary. > > > > I believe we should have clean testcases which handle the exceptions > > gracefully or consumes the exceptions if they are not useful at all. I > can > > start with identifying such test cases to start with and start handling > > exceptions correspondingly. > > > > Again, I don't know if this point has come up before as well and am I > just > > repeating the discussion. > > > > Please share your thoughts. > > Regards, > > > > > > -- > - > Jaideep Dhok > > -- > _____________________________________________________________ > The information contained in this communication is intended solely for the > use of the individual or entity to whom it is addressed and others > authorized to receive it. It may contain confidential or legally privileged > information. If you are not the intended recipient you are hereby notified > that any disclosure, copying, distribution or taking any action in reliance > on the contents of this information is strictly prohibited and may be > unlawful. If you have received this communication in error, please notify > us immediately by responding to this email and then delete it from your > system. The firm is neither liable for the proper and complete transmission > of the information contained in this communication nor for any delay in its > receipt. >
