aboutsummaryrefslogtreecommitdiff
path: root/R/run-tests.sh
diff options
context:
space:
mode:
authorShivaram Venkataraman <shivaram@cs.berkeley.edu>2016-08-22 17:09:32 -0700
committerShivaram Venkataraman <shivaram@cs.berkeley.edu>2016-08-22 17:09:32 -0700
commit920806ab272ba58a369072a5eeb89df5e9b470a6 (patch)
tree589a3558e62b560ca9d006202825ebe0988edb60 /R/run-tests.sh
parent37f0ab70d25802b609317bc93421d2fe3ee9db6e (diff)
downloadspark-920806ab272ba58a369072a5eeb89df5e9b470a6.tar.gz
spark-920806ab272ba58a369072a5eeb89df5e9b470a6.tar.bz2
spark-920806ab272ba58a369072a5eeb89df5e9b470a6.zip
[SPARK-16577][SPARKR] Add CRAN documentation checks to run-tests.sh
## What changes were proposed in this pull request? (Please fill in changes proposed in this fix) ## How was this patch tested? This change adds CRAN documentation checks to be run as a part of `R/run-tests.sh` . As this script is also used by Jenkins this means that we will get documentation checks on every PR going forward. (If this patch involves UI changes, please attach a screenshot; otherwise, remove this) Author: Shivaram Venkataraman <shivaram@cs.berkeley.edu> Closes #14759 from shivaram/sparkr-cran-jenkins.
Diffstat (limited to 'R/run-tests.sh')
-rwxr-xr-xR/run-tests.sh27
1 files changed, 24 insertions, 3 deletions
diff --git a/R/run-tests.sh b/R/run-tests.sh
index 9dcf0ace7d..1a1e8ab9ff 100755
--- a/R/run-tests.sh
+++ b/R/run-tests.sh
@@ -26,6 +26,17 @@ rm -f $LOGFILE
SPARK_TESTING=1 $FWDIR/../bin/spark-submit --driver-java-options "-Dlog4j.configuration=file:$FWDIR/log4j.properties" --conf spark.hadoop.fs.default.name="file:///" $FWDIR/pkg/tests/run-all.R 2>&1 | tee -a $LOGFILE
FAILED=$((PIPESTATUS[0]||$FAILED))
+# Also run the documentation tests for CRAN
+CRAN_CHECK_LOG_FILE=$FWDIR/cran-check.out
+rm -f $CRAN_CHECK_LOG_FILE
+
+NO_TESTS=1 NO_MANUAL=1 $FWDIR/check-cran.sh 2>&1 | tee -a $CRAN_CHECK_LOG_FILE
+FAILED=$((PIPESTATUS[0]||$FAILED))
+
+NUM_CRAN_WARNING="$(grep -c WARNING$ $CRAN_CHECK_LOG_FILE)"
+NUM_CRAN_ERROR="$(grep -c ERROR$ $CRAN_CHECK_LOG_FILE)"
+NUM_CRAN_NOTES="$(grep -c NOTE$ $CRAN_CHECK_LOG_FILE)"
+
if [[ $FAILED != 0 ]]; then
cat $LOGFILE
echo -en "\033[31m" # Red
@@ -33,7 +44,17 @@ if [[ $FAILED != 0 ]]; then
echo -en "\033[0m" # No color
exit -1
else
- echo -en "\033[32m" # Green
- echo "Tests passed."
- echo -en "\033[0m" # No color
+ # We have 2 existing NOTEs for new maintainer, attach()
+ # We have one more NOTE in Jenkins due to "No repository set"
+ if [[ $NUM_CRAN_WARNING != 0 || $NUM_CRAN_ERROR != 0 || $NUM_CRAN_NOTES -gt 3 ]]; then
+ cat $CRAN_CHECK_LOG_FILE
+ echo -en "\033[31m" # Red
+ echo "Had CRAN check errors; see logs."
+ echo -en "\033[0m" # No color
+ exit -1
+ else
+ echo -en "\033[32m" # Green
+ echo "Tests passed."
+ echo -en "\033[0m" # No color
+ fi
fi