Kafka, mail # dev - Re: Unit test failure stack traces - 2013-01-27, 18:23
 Search Hadoop and all its subprojects:

Switch to Threaded View
Copy link to this message
-
Re: Unit test failure stack traces
Hi Neha,

did some digging and came accross this.

./sbt
set every traceLevel := 10
test

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
tracesĀ¶<http://www.scala-sbt.org/release/docs/Howto/logging.html#trace>

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
frames.

For example, the following configures sbt to show stack traces up to the
first sbt frame:
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
traceLevel appropriately:

On Fri, Jan 25, 2013 at 7:23 PM, Joe Stein <[EMAIL PROTECTED]> wrote:

/*
Joe Stein
http://www.linkedin.com/in/charmalloc
Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
*/

 
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB