Running dev/run-tests as-is should work and will test everything. That's
what the contributing guide recommends, if I remember correctly.
At some point we should make it easier to test individual components
locally using the dev script, but calling sbt on the various tests suites
as Michael
_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
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
