Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9478#issuecomment-153982455
**[Test build #45106 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45106/consoleFull)**
for PR 9478 at commit
Github user jbonofre commented on the pull request:
https://github.com/apache/spark/pull/9117#issuecomment-153983273
Thanks @kayousterhout. I promise it's my last mistake ;)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9477#issuecomment-153987324
Merged build triggered.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9477#issuecomment-153987350
Merged build started.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9489#issuecomment-153987317
Merged build triggered.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9489#issuecomment-153987351
Merged build started.
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8559#issuecomment-153990942
**[Test build #45102 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45102/consoleFull)**
for PR 8559 at commit
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9476#discussion_r43989299
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/DStreamGraph.scala ---
@@ -167,7 +167,8 @@ final private[streaming] class DStreamGraph extends
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8314#issuecomment-153999510
@squito very nice work here. I think the SparkR tests finally need a
similar treatment and it's good to go. Thankfully I think the errors are quite
plain about what they
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9417
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9477#issuecomment-153983073
**[Test build #1983 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1983/consoleFull)**
for PR 9477 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9460#issuecomment-153985119
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9460#issuecomment-153985115
Merged build finished. Test PASSed.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9477#issuecomment-153996532
Merged build finished. Test PASSed.
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9432#issuecomment-154003198
**[Test build #1984 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1984/consoleFull)**
for PR 9432 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9487#issuecomment-154003441
**[Test build #1985 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1985/consoleFull)**
for PR 9487 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-154007286
CC @chenghao-intel
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9489#issuecomment-153988698
Merged build triggered.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9489#issuecomment-153988731
Merged build started.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9489#issuecomment-153991209
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9489#issuecomment-153991207
Merged build finished. Test FAILed.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9477#issuecomment-153991110
Merged build triggered.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8559#issuecomment-153991054
Merged build finished. Test PASSed.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9477#issuecomment-153991140
Merged build started.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8559#issuecomment-153991056
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9489#issuecomment-153991118
**[Test build #45109 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45109/consoleFull)**
for PR 9489 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9488#issuecomment-153992127
It looks reasonable, and is not even something we'd have to wait for 2.0
for. I recall that we had not done this yet, and targeted it for 2.0, because
it required
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8314#issuecomment-153998245
**[Test build #45101 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45101/consoleFull)**
for PR 8314 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9396
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8314#issuecomment-153998444
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9396#issuecomment-153998278
Merged to master
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9478#issuecomment-153982287
Merged build triggered.
---
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
Github user sun-rui commented on the pull request:
https://github.com/apache/spark/pull/9390#issuecomment-153982727
submitted https://issues.apache.org/jira/browse/SPARK-11525: Support spark
packages containing R source code in Standalone mode
---
If your project is set up for it,
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9460#issuecomment-153985001
**[Test build #45099 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45099/consoleFull)**
for PR 9460 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9214#issuecomment-153987620
**[Test build #45100 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45100/consoleFull)**
for PR 9214 at commit
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/9477#issuecomment-153990700
@JoshRosen I should had addressed your comments, will merge this once pass
the tests.
---
If your project is set up for it, you can reply to this email and have your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9477#issuecomment-153995771
**[Test build #45096 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45096/consoleFull)**
for PR 9477 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9489#issuecomment-153998372
**[Test build #45109 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45109/consoleFull)**
for PR 9489 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8314#issuecomment-153998440
Merged build finished. Test FAILed.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9489#issuecomment-153998475
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9489#issuecomment-153998474
Merged build finished. Test FAILed.
---
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
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9417#issuecomment-154001929
Merged to master
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8780#issuecomment-154004331
**[Test build #1986 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1986/consoleFull)**
for PR 8780 at commit
GitHub user zjffdu opened a pull request:
https://github.com/apache/spark/pull/9490
[SPARK-11102] [SQL] Uninformative exception when specifing non-exist
Rebase the code base and create another PR
You can merge this pull request into a Git repository by running:
$ git pull
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-154008528
**[Test build #45111 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45111/consoleFull)**
for PR 9490 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9478#issuecomment-154009796
**[Test build #45106 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45106/consoleFull)**
for PR 9478 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9478#issuecomment-154009895
Merged build finished. Test FAILed.
---
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
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/7786#issuecomment-153984512
Hi @mccheah sorry for late response, looks like this message is out of my
radar.
From Yarn's side, Yarn makes this preemption decision depends on status of
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9214#issuecomment-153987949
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9477#issuecomment-153987965
**[Test build #45108 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45108/consoleFull)**
for PR 9477 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9214#issuecomment-153987943
Merged build finished. Test PASSed.
---
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
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9336#issuecomment-154001195
Merged to master / 1.5
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9336
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9456#issuecomment-154003232
**[Test build #1987 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1987/consoleFull)**
for PR 9456 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8780#issuecomment-154003137
**[Test build #1986 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1986/consoleFull)**
for PR 8780 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-154005153
Merged build started.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-154005130
Merged build triggered.
---
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
Github user jbonofre commented on the pull request:
https://github.com/apache/spark/pull/9487#issuecomment-153984694
Reference to the "old" PR: https://github.com/apache/spark/pull/9117
---
If your project is set up for it, you can reply to this email and have your
reply appear on
GitHub user felixcheung opened a pull request:
https://github.com/apache/spark/pull/9489
[SPARK-11468][SPARKR] add stddev/variance agg functions for Column
Checked names, none of them should conflict with anything in base
@shivaram @davies @rxin
You can merge this pull
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9477#issuecomment-153992590
**[Test build #45110 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45110/consoleFull)**
for PR 9477 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9477#issuecomment-153996536
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user zjffdu closed the pull request at:
https://github.com/apache/spark/pull/9223
---
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
Github user zjffdu commented on the pull request:
https://github.com/apache/spark/pull/9223#issuecomment-154004758
Close it as needs to rebase the code base. Open #9490
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9191#issuecomment-154004973
Note this duplicates https://github.com/apache/spark/pull/5622
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9097#issuecomment-154008840
Merged build finished. Test PASSed.
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9097#issuecomment-154008603
**[Test build #45104 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45104/consoleFull)**
for PR 9097 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9097#issuecomment-154008845
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9478#issuecomment-154009898
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user jbonofre commented on the pull request:
https://github.com/apache/spark/pull/9487#issuecomment-154070111
Updated PR implementing Kay's suggestions: formatting the locality level
summary string, and moving under the "Show Additional Metrics" drop down.
---
If your project
Github user jbonofre commented on the pull request:
https://github.com/apache/spark/pull/9165#issuecomment-154073618
Thoughts ?
---
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
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9487#discussion_r44016799
--- Diff: core/src/main/scala/org/apache/spark/ui/jobs/StagePage.scala ---
@@ -70,6 +71,33 @@ private[ui] class StagePage(parent: StagesTab) extends
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9165#discussion_r44017009
--- Diff: core/src/main/resources/org/apache/spark/ui/static/sorttable.js
---
@@ -3,19 +3,19 @@
version 2
7th April 2007
Stuart
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9165#discussion_r44017076
--- Diff: core/src/main/resources/org/apache/spark/ui/static/sorttable.js
---
@@ -81,18 +81,18 @@ sorttable = {
if
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9165#discussion_r44017175
--- Diff: core/src/main/resources/org/apache/spark/ui/static/sorttable.js
---
@@ -100,20 +100,20 @@ sorttable = {
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9165#issuecomment-154077899
Hm, by the end here it seems like 90% of the changes are whitespace
changes. It's enough compared to the small functional change that I think it's
worth re-doing.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9477#issuecomment-154048664
**[Test build #45108 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45108/consoleFull)**
for PR 9477 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9477#issuecomment-154048716
Merged build finished. Test FAILed.
---
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
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9191#issuecomment-154050466
OK, Josh also closed the other one. One JIRA is open now. At least have <=
1 PR.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9456
---
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
GitHub user yanboliang opened a pull request:
https://github.com/apache/spark/pull/9492
[SPARK-11527] [ML] [PySpark] PySpark AFTSurvivalRegressionModel should
expose coefficients/intercept/scale
PySpark AFTSurvivalRegressionModel should expose
coefficients/intercept/scale.
You
Github user jbonofre commented on a diff in the pull request:
https://github.com/apache/spark/pull/9487#discussion_r44003767
--- Diff: core/src/main/scala/org/apache/spark/ui/jobs/StagePage.scala ---
@@ -70,6 +71,17 @@ private[ui] class StagePage(parent: StagesTab) extends
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9477#issuecomment-154048718
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user viper-kun closed the pull request at:
https://github.com/apache/spark/pull/9191
---
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
Github user viper-kun commented on the pull request:
https://github.com/apache/spark/pull/9191#issuecomment-154050289
ok. close it
---
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
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9456#issuecomment-154050274
Merged to master
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9494#issuecomment-154052730
**[Test build #45114 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45114/consoleFull)**
for PR 9494 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9494#issuecomment-154053072
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9494#issuecomment-154053070
Merged build finished. Test PASSed.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9477#issuecomment-154054815
Merged build finished. Test FAILed.
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9477#issuecomment-154054716
**[Test build #45110 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45110/consoleFull)**
for PR 9477 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9477#issuecomment-154054818
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-154015117
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9490#issuecomment-154015079
**[Test build #45111 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45111/consoleFull)**
for PR 9490 at commit
GitHub user yanboliang opened a pull request:
https://github.com/apache/spark/pull/9491
[SPARK-10689] [ML] [Doc] User guide and example code for
AFTSurvivalRegression
Add user guide and example code for ```AFTSurvivalRegression```.
You can merge this pull request into a Git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9491#issuecomment-154017878
Merged build started.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9491#issuecomment-154017829
Merged build triggered.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9390#issuecomment-154023464
Merged build finished. Test PASSed.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9390#issuecomment-154023468
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9492#issuecomment-154025892
**[Test build #45113 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45113/consoleFull)**
for PR 9492 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9493#issuecomment-154026004
Merged build triggered.
---
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
1 - 100 of 1008 matches
Mail list logo
