I heard from one person offline who regularly builds Spark on OSX and Linux and they felt like they only ever saw this error on OSX; if anyone can confirm whether they've seen it on Linux, that would be good to know.
Stephen: good to know re: profiles/options. I don't think changing them is a necessary condition as I believe I've run into it without doing that, but any set of steps to reproduce this would be welcome so that we could escalate to Typesafe as appropriate. On Sun, Oct 26, 2014 at 11:46 PM, Stephen Boesch <java...@gmail.com> wrote: > Yes it is necessary to do a mvn clean when encountering this issue. > Typically you would have changed one or more of the profiles/options - > which leads to this occurring. > > 2014-10-22 22:00 GMT-07:00 Ryan Williams <ryan.blake.willi...@gmail.com>: > > 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 <https://gist.github.com/ryan-williams/7673d7da928570907f4d> is a >> full gist of an innocuous test command (mvn test >> -Dsuites='*KafkaStreamSuite') exhibiting this behavior. Problem starts >> on L512 >> <https://gist.github.com/ryan-williams/7673d7da928570907f4d#file-stdout-L512> >> and there’s a final stack trace at the bottom >> <https://gist.github.com/ryan-williams/7673d7da928570907f4d#file-stdout-L671> >> . >> >> 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 >> <http://apache-spark-user-list.1001560.n3.nabble.com/spark-github-source-build-error-td10532.html> >> on this list is basically the same error, but in TestSQLContext.scala >> and this SO post >> <http://stackoverflow.com/questions/25211071/compilation-errors-in-spark-datatypeconversions-scala-on-intellij-when-using-m> >> 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? >> >> > >
