We don't really use scalafmt, but there's a config and profile for it. I am not sure if it will necessarily do the right thing in all cases. You haven't shown the scalastyle failure, but if you've changed the code, that's probably it. It is passing locally and on master.
On Sat, May 16, 2020 at 12:58 PM suddhu <sudhar...@gmail.com> wrote: > > Hello :) > > I'm running this example form the official site: > https://spark.apache.org/developer-tools.html > > testOnly *DAGSchedulerSuite -- -z "SPARK-12345" > > But I get: > [error] (catalyst/*:scalaStyleOnTest) Failing because of negative scalastyle > result > > This happens even *after* running ./dev/scalafmt > > Any reasons why? Sometimes I also get an error message that a line in the > code is >100 char long. But isnt this the kind of thing that scalafmt should > fix? Also, my scalastyle-on-compile.generated.xml, scalastyle-output.xml, > scalastyle.txt all seem to be empty. > > > > > -- > Sent from: http://apache-spark-developers-list.1001551.n3.nabble.com/ > > --------------------------------------------------------------------- > To unsubscribe e-mail: dev-unsubscr...@spark.apache.org > --------------------------------------------------------------------- To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
