spark-instrumented-optimizer/dev/appveyor-guide.md
hyukjinkwon 78d5d4dd5c [SPARK-17200][PROJECT INFRA][BUILD][SPARKR] Automate building and testing on Windows (currently SparkR only)
## What changes were proposed in this pull request?

This PR adds the build automation on Windows with [AppVeyor](https://www.appveyor.com/) CI tool.

Currently, this only runs the tests for SparkR as we have been having some issues with testing Windows-specific PRs (e.g. https://github.com/apache/spark/pull/14743 and https://github.com/apache/spark/pull/13165) and hard time to verify this.

One concern is, this build is dependent on [steveloughran/winutils](https://github.com/steveloughran/winutils) for pre-built Hadoop bin package (who is a Hadoop PMC member).

## How was this patch tested?

Manually, https://ci.appveyor.com/project/HyukjinKwon/spark/build/88-SPARK-17200-build-profile
This takes roughly 40 mins.

Some tests are already being failed and this was found in https://github.com/apache/spark/pull/14743#issuecomment-241405287.

Author: hyukjinkwon <gurwls223@gmail.com>

Closes #14859 from HyukjinKwon/SPARK-17200-build.
2016-09-08 08:26:59 -07:00

7.9 KiB

AppVeyor Guides

Currently, SparkR on Windows is being tested with AppVeyor. This page describes how to set up AppVeyor with Spark, how to run the build, check the status and stop the build via this tool. There is the documenation for AppVeyor here. Please refer this for full details.

Setting up AppVeyor

Sign up AppVeyor.

  • Go to https://ci.appveyor.com, and then click "SIGN UP FOR FREE".

    2016-09-04 11 07 48
  • As Apache Spark is one of open source projects, click "FREE - for open-source projects".

    2016-09-04 11 07 58
  • Click "Github".

    2016-09-04 11 08 10
  • Click your account and then click "Profile".

    2016-09-04 11 09 43
  • Enable the link with GitHub via clicking "Link Github account".

    2016-09-04 11 09 52
  • Click "Authorize application" in Github site.

2016-09-04 11 10 05

Add a project, Spark to enable the builds.

  • Go to the PROJECTS menu.

    2016-08-30 12 16 31
  • Click "NEW PROJECT" to add Spark.

    2016-08-30 12 16 35
  • Since we will use Github here, click the "GITHUB" button and then click "Authorize Github" so that AppVeyor can access to the Github logs (e.g. commits).

    2016-09-04 11 10 22
  • Click "Authorize application" from Github (the above step will pop up this page).

    2016-09-04 11 10 27
  • Come back to https://ci.appveyor.com/projects/new and then adds "spark".

    2016-09-04 11 10 36

Check if any event supposed to run the build actually triggers the build.

  • Click "PROJECTS" menu.

    2016-08-30 12 16 31
  • Click Spark project.

    2016-09-04 11 22 37

Checking the status, restarting and stopping the build

  • Click "PROJECTS" menu.

    2016-08-30 12 16 31
  • Locate "spark" and click it.

    2016-09-04 11 22 37
  • Here, we can check the status of current build. Also, "HISTORY" shows the past build history.

    2016-09-04 11 23 24
  • If the build is stopped, "RE-BUILD COMMIT" button appears. Click this button to restart the build.

    2016-08-30 12 29 41
  • If the build is running, "CANCEL BUILD" buttom appears. Click this button top cancel the current build.

    2016-08-30 1 11 13

Specifying the branch for building and setting the build schedule

Note: It seems the configurations in UI and appveyor.yml are mutually exclusive according to the documentation.

  • Click the settings button on the right.

    2016-08-30 1 19 12
  • Set the default branch to build as above.

    2016-08-30 12 42 25
  • Specify the branch in order to exclude the builds in other branches.

    2016-08-30 12 42 33
  • Set the Crontab expression to regularly start the build. AppVeyor uses Crontab expression, atifaziz/NCrontab. Please refer the examples here.

    2016-08-30 12 42 43

Filtering commits and Pull Requests

Currently, AppVeyor is only used for SparkR. So, the build is only triggered when R codes are changed.

This is specified in .appveyor.yml as below:

only_commits:
  files:
    - R/

Please refer https://www.appveyor.com/docs/how-to/filtering-commits for more details.

Checking the full log of the build

Currently, the console in AppVeyor does not print full details. This can be manually checked. For example, AppVeyor shows the failed tests as below in console

Failed -------------------------------------------------------------------------
1. Error: union on two RDDs (@test_binary_function.R#38) -----------------------
1: textFile(sc, fileName) at C:/projects/spark/R/lib/SparkR/tests/testthat/test_binary_function.R:38
2: callJMethod(sc, "textFile", path, getMinPartitions(sc, minPartitions))
3: invokeJava(isStatic = FALSE, objId$id, methodName, ...)
4: stop(readString(conn))

After downloading the log by clicking the log button as below:

2016-09-08 11 37 17

the details can be checked as below (e.g. exceptions)

Failed -------------------------------------------------------------------------
1. Error: spark.lda with text input (@test_mllib.R#655) ------------------------
 org.apache.spark.sql.AnalysisException: Path does not exist: file:/C:/projects/spark/R/lib/SparkR/tests/testthat/data/mllib/sample_lda_data.txt;
    at org.apache.spark.sql.execution.datasources.DataSource$$anonfun$12.apply(DataSource.scala:376)
    at org.apache.spark.sql.execution.datasources.DataSource$$anonfun$12.apply(DataSource.scala:365)
    at scala.collection.TraversableLike$$anonfun$flatMap$1.apply(TraversableLike.scala:241)
    at scala.collection.TraversableLike$$anonfun$flatMap$1.apply(TraversableLike.scala:241)
    ...

 1: read.text("data/mllib/sample_lda_data.txt") at C:/projects/spark/R/lib/SparkR/tests/testthat/test_mllib.R:655
 2: dispatchFunc("read.text(path)", x, ...)
 3: f(x, ...)
 4: callJMethod(read, "text", paths)
 5: invokeJava(isStatic = FALSE, objId$id, methodName, ...)
 6: stop(readString(conn))