Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/16014#discussion_r91196396
--- Diff: dev/create-release/release-build.sh ---
@@ -221,14 +235,13 @@ if [[ "$1" == "package" ]]; then
# We increment the Zinc port each time to avoid OOM's and other
craziness if multiple builds
# share the same Zinc server.
- # Make R source package only once. (--r)
FLAGS="-Psparkr -Phive -Phive-thriftserver -Pyarn -Pmesos"
make_binary_release "hadoop2.3" "-Phadoop-2.3 $FLAGS" "3033" &
make_binary_release "hadoop2.4" "-Phadoop-2.4 $FLAGS" "3034" &
make_binary_release "hadoop2.6" "-Phadoop-2.6 $FLAGS" "3035" &
make_binary_release "hadoop2.7" "-Phadoop-2.7 $FLAGS" "3036" "withpip" &
make_binary_release "hadoop2.4-without-hive" "-Psparkr -Phadoop-2.4
-Pyarn -Pmesos" "3037" &
- make_binary_release "without-hadoop" "--r -Psparkr -Phadoop-provided
-Pyarn -Pmesos" "3038" &
+ make_binary_release "without-hadoop" "-Psparkr -Phadoop-provided -Pyarn
-Pmesos" "3038" "withr" &
--- End diff --
It was mostly to use a "separate profile" from "withpip"
Running this `R CMD build` would run some Spark code (mainly in vignettes
since tests are not run in `R CMD check`), but nothing that depends on the file
system etc.
Also the Spark jar, while loaded and called into during the process, will
not be packaged into the resulting R source package, so I thought it didn't
matter which build profile we would run this in.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
