RE: Are we running SparkR tests in Jenkins?

2016-01-17 Thread Felix Cheung
I think that breaks sparkR, the commandline script, and Jenkins, in which run-test.sh is calling sparkR. I'll work on this - since this also affects my PR #10652... Date: Fri, 15 Jan 2016 15:33:13 -0800 Subject: Re: Are we running SparkR tests in Jenkins? From: zjf...@gmail.com To: shiva

Re: Are we running SparkR tests in Jenkins?

2016-01-15 Thread Reynold Xin
+Shivaram Ah damn - we should fix it. This was broken by https://github.com/apache/spark/pull/10658 - which removed a functionality that has been deprecated since Spark 1.0. On Fri, Jan 15, 2016 at 3:19 PM, Herman van Hövell tot Westerflier < hvanhov...@questtec.nl> wrote: > Hi all, > > I

Re: Are we running SparkR tests in Jenkins?

2016-01-15 Thread Shivaram Venkataraman
Yes - we should be running R tests AFAIK. That error message is a deprecation warning about the script `bin/sparkR` which needs to be changed in https://github.com/apache/spark/blob/7cd7f2202547224593517b392f56e49e4c94cabc/R/run-tests.sh#L26 to bin/spark-submit. Thanks Shivaram On Fri, Jan 15,

Re: Are we running SparkR tests in Jenkins?

2016-01-15 Thread Jeff Zhang
Created https://issues.apache.org/jira/browse/SPARK-12846 On Fri, Jan 15, 2016 at 3:29 PM, Jeff Zhang wrote: > Right, I forget the documentation, will create a follow up jira. > > On Fri, Jan 15, 2016 at 3:23 PM, Shivaram Venkataraman < > shiva...@eecs.berkeley.edu> wrote: >

Re: Are we running SparkR tests in Jenkins?

2016-01-15 Thread Shivaram Venkataraman
Ah I see. I wasn't aware of that PR. We should do a find and replace in all the documentation and rest of the repository as well. Shivaram On Fri, Jan 15, 2016 at 3:20 PM, Reynold Xin wrote: > +Shivaram > > Ah damn - we should fix it. > > This was broken by

Re: Are we running SparkR tests in Jenkins?

2016-01-15 Thread Jeff Zhang
Right, I forget the documentation, will create a follow up jira. On Fri, Jan 15, 2016 at 3:23 PM, Shivaram Venkataraman < shiva...@eecs.berkeley.edu> wrote: > Ah I see. I wasn't aware of that PR. We should do a find and replace > in all the documentation and rest of the repository as well. > >