@@ -58,7 +58,7 @@ if [ -n "$AMPLAB_JENKINS" ]; then
58
58
diffs=` git diff --name-only master | grep " ^sql/" `
59
59
if [ -n " $diffs " ]; then
60
60
echo " Detected changes in SQL. Will run Hive test suite."
61
- export _RUN_SQL_TESTS=true # exported for PySpark tests
61
+ _RUN_SQL_TESTS=true
62
62
fi
63
63
fi
64
64
@@ -89,13 +89,22 @@ echo "========================================================================="
89
89
echo " Running Spark unit tests"
90
90
echo " ========================================================================="
91
91
92
+ # Build Spark; we always build with Hive because the PySpark SparkSQL tests need it.
93
+ # echo "q" is needed because sbt on encountering a build file with failure
94
+ # (either resolution or compilation) prompts the user for input either q, r,
95
+ # etc to quit or retry. This echo is there to make it not block.
96
+ BUILD_MVN_PROFILE_ARGS=" $SBT_MAVEN_PROFILES_ARGS -Phive -Phive-thriftserver "
97
+ echo -e " q\n" | sbt/sbt $BUILD_MVN_PROFILE_ARGS clean package assembly/assembly | \
98
+ grep -v -e " info.*Resolving" -e " warn.*Merging" -e " info.*Including"
99
+
100
+ # If the Spark SQL tests are enabled, run the tests with the Hive profiles enabled:
92
101
if [ -n " $_RUN_SQL_TESTS " ]; then
93
102
SBT_MAVEN_PROFILES_ARGS=" $SBT_MAVEN_PROFILES_ARGS -Phive -Phive-thriftserver"
94
103
fi
95
- # echo "q" is needed because sbt on encountering a build file with failure
96
- # (either resolution or compilation) prompts the user for input either q, r,
104
+ # echo "q" is needed because sbt on encountering a build file with failure
105
+ # (either resolution or compilation) prompts the user for input either q, r,
97
106
# etc to quit or retry. This echo is there to make it not block.
98
- echo -e " q\n" | sbt/sbt $SBT_MAVEN_PROFILES_ARGS clean package assembly/assembly test | \
107
+ echo -e " q\n" | sbt/sbt $SBT_MAVEN_PROFILES_ARGS test | \
99
108
grep -v -e " info.*Resolving" -e " warn.*Merging" -e " info.*Including"
100
109
101
110
echo " "
0 commit comments