Hey Ryan, I've found that filing issues with the Scala/Typesafe JIRA is pretty helpful if the issue can be fully reproduced, and even sometimes helpful if it can't. You can file bugs here:
https://issues.scala-lang.org/secure/Dashboard.jspa The Spark SQL code in particular is typically the source of these, as we use more fancy scala features. In a pinch it is also possible to recompile and test code without building SQL if you just run tests for the specific module (e.g. streaming). In sbt this sort of "just works": sbt/sbt "streaming/test-only a.b.c*" In maven it's more clunky but if you do a "mvn install" first then (I think) you can test sub-modules independently: mvn test -pl streaming ... - Patrick On Wed, Oct 22, 2014 at 10:00 PM, Ryan Williams <ryan.blake.willi...@gmail.com> wrote: > I started building Spark / running Spark tests this weekend and on maybe > 5-10 occasions have run into a compiler crash while compiling > DataTypeConversions.scala. > > Here is a full gist of an innocuous test command (mvn test > -Dsuites='*KafkaStreamSuite') exhibiting this behavior. Problem starts on > L512 and there's a final stack trace at the bottom. > > mvn clean or ./sbt/sbt clean "fix" it (I believe I've observed the issue > while compiling with each tool), but are annoying/time-consuming to do, > obvs, and it's happening pretty frequently for me when doing only small > numbers of incremental compiles punctuated by e.g. checking out different > git commits. > > Have other people seen this? This post on this list is basically the same > error, but in TestSQLContext.scala and this SO post claims to be hitting it > when trying to build in intellij. > > It seems likely to be a bug in scalac; would finding a consistent repro case > and filing it somewhere be useful? --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@spark.apache.org For additional commands, e-mail: user-h...@spark.apache.org
