Neha Narkhede 2013-01-25, 17:40
Joe Stein 2013-01-26, 00:23
-Re: Unit test failure stack traces
Joe Stein 2013-01-27, 18:23
did some digging and came accross this.
set every traceLevel := 10
we can either document it on our wiki or we can set the trace level to a
higher number in build.sbt (i.e. traceLevel := 10)
let me know how it goes
excerpt from http://www.scala-sbt.org/release/docs/Howto/logging.html#trace
Configure printing of stack
By default, sbt hides the stack trace of most exceptions thrown during
execution. It prints a message that indicates how to display the exception.
However, you may want to show more of stack traces by default.
The setting to configure is traceLevel, which is a setting with an Int
value. When traceLevel is set to a negative value, no stack traces are
shown. When it is zero, the stack trace is displayed up to the first sbt
stack frame. When positive, the stack trace is shown up to that many stack
For example, the following configures sbt to show stack traces up to the
first sbt frame:
> set every traceLevel := 0
The every part means to override the setting in all scopes. To change the
trace printing behavior for a single project, configuration, or task, scope
> set traceLevel in Test := 5> set traceLevel in update := 0> set traceLevel in ThisProject := -1
On Fri, Jan 25, 2013 at 7:23 PM, Joe Stein <[EMAIL PROTECTED]> wrote:
> Not sure off hand will look into it.
> Joe Stein, Chief Architect
> Twitter: @allthingshadoop
> Mobile: 917-597-9771
> On Jan 25, 2013, at 12:39 PM, Neha Narkhede <[EMAIL PROTECTED]>
> > Hi Joe,
> > The SBT upgrade patch broke the behavior of unit tests and I'm not sure
> > to proceed here. If unit tests fail, sbt hides the stack traces now,
> > is good. But what is the command that can print those per test ?
> > Thanks,
> > Neha
Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>