Also, in general for SQL only changes it is sufficient to run "sbt/sbt catatlyst/test sql/test hive/test". The "hive/test" part takes the longest, so I usually leave that out until just before submitting unless my changes are hive specific.
On Thu, Oct 9, 2014 at 11:40 AM, Nicholas Chammas < nicholas.cham...@gmail.com> wrote: > _RUN_SQL_TESTS needs to be true as well. Those two _... variables set get > correctly when tests are run on Jenkins. They’re not meant to be > manipulated directly by testers. > > Did you want to run SQL tests only locally? You can try faking being > Jenkins by setting AMPLAB_JENKINS=true before calling run-tests. That > should be simpler than futzing with the _... variables. > > Nick > > > On Thu, Oct 9, 2014 at 10:10 AM, Yana <yana.kadiy...@gmail.com> wrote: > > > Hi, apologies if I missed a FAQ somewhere. > > > > I am trying to submit a bug fix for the very first time. Reading > > instructions, I forked the git repo (at > > c9ae79fba25cd49ca70ca398bc75434202d26a97) and am trying to run tests. > > > > I run this: ./dev/run-tests _SQL_TESTS_ONLY=true > > > > and after a while get the following error: > > > > [info] ScalaTest > > [info] Run completed in 3 minutes, 37 seconds. > > [info] Total number of tests run: 224 > > [info] Suites: completed 19, aborted 0 > > [info] Tests: succeeded 224, failed 0, canceled 0, ignored 5, pending 0 > > [info] All tests passed. > > [info] Passed: Total 224, Failed 0, Errors 0, Passed 224, Ignored 5 > > [success] Total time: 301 s, completed Oct 9, 2014 9:31:23 AM > > [error] Expected ID character > > [error] Not a valid command: hive-thriftserver > > [error] Expected project ID > > [error] Expected configuration > > [error] Expected ':' (if selecting a configuration) > > [error] Expected key > > [error] Not a valid key: hive-thriftserver > > [error] hive-thriftserver/test > > [error] ^ > > > > > > (I am running this without my changes) > > > > I have 2 questions: > > 1. How to fix this > > 2. Is there a best practice on what to fork so you start off with a "good > > state"? I'm wondering if I should sync the latest changes or go back to a > > label? > > > > thanks in advance > > > > > > > > > > -- > > View this message in context: > > > http://apache-spark-developers-list.1001551.n3.nabble.com/Trouble-running-tests-tp8717.html > > Sent from the Apache Spark Developers List mailing list archive at > > Nabble.com. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org > > For additional commands, e-mail: dev-h...@spark.apache.org > > > > >
