GitHub user guowei2 opened a pull request:
https://github.com/apache/spark/pull/2953
Spark 1442 step 1
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/guowei2/spark SPARK-1442-STEP-1
Alternatively you can review and apply these
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2922#issuecomment-60553565
[Test build #22277 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22277/consoleFull)
for PR 2922 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2953#issuecomment-60553550
Can one of the admins verify this patch?
---
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 guowei2 commented on the pull request:
https://github.com/apache/spark/pull/2953#issuecomment-60553573
aims of step1 ( this pr):
1ãsupport parse sql with complex window define
2ãsupport most of aggregate-functions with window-spec
3ãsupport window range
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/2933#issuecomment-60553581
@JoshRosen I think we still have it (in tests at tonight):
```
[info] org.apache.spark.SparkException: Job aborted due to stage failure:
Task 0 in stage 11.0
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/2922#issuecomment-60553667
@pwendell - I made destroy blocking by default and only made that version
public (its not clear we need the non-blocking version to also be public -- we
can add it
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2933#issuecomment-60553702
This is really strange; I thought that the unexpected exception type
would have been addressed by https://github.com/apache/spark/pull/2932
---
If your project is set
Github user sryza commented on a diff in the pull request:
https://github.com/apache/spark/pull/2746#discussion_r19389557
--- Diff:
core/src/main/scala/org/apache/spark/ExecutorAllocationManager.scala ---
@@ -0,0 +1,409 @@
+/*
+ * Licensed to the Apache Software Foundation
Github user sryza commented on a diff in the pull request:
https://github.com/apache/spark/pull/2746#discussion_r19389583
--- Diff:
core/src/main/scala/org/apache/spark/ExecutorAllocationManager.scala ---
@@ -0,0 +1,409 @@
+/*
+ * Licensed to the Apache Software Foundation
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2933#issuecomment-60553953
Can you point me to the commit that produced that stacktrace?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
GitHub user WangTaoTheTonic opened a pull request:
https://github.com/apache/spark/pull/2954
[SPARK-4095][YARN][Minor]extract val isLaunchingDriver in ClientBase
Instead of checking if `args.userClass` is null repeatedly, we extract it
to an global val as in `ApplicationMaster`.
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/2933#issuecomment-60554225
@JoshRosen @pwendell The test branch (internal) did not have that commit.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2954#issuecomment-60554332
[Test build #22278 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22278/consoleFull)
for PR 2954 at commit
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/2762#issuecomment-60554357
test this please.
---
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
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/2922#issuecomment-60554586
Oh right yeah. Great, LGTM.
---
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/2716#issuecomment-60554724
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/2716#issuecomment-60554714
[Test build #22273 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22273/consoleFull)
for PR 2716 at commit
Github user anantasty commented on the pull request:
https://github.com/apache/spark/pull/2942#issuecomment-60554980
Should we create another PR for the python bindings/example?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/2771#issuecomment-6072
test this please.
---
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
GitHub user WangTaoTheTonic opened a pull request:
https://github.com/apache/spark/pull/2955
[SPARK-4096][YARN]Update executor memory description in the help message
Here `ApplicationMaster` accept executor memory argument only in number
format, we should update the description in
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2955#issuecomment-60555883
[Test build #22279 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22279/consoleFull)
for PR 2955 at commit
GitHub user liyezhang556520 opened a pull request:
https://github.com/apache/spark/pull/2956
[SPARK-4094][CORE] checkpoint should still be available after any rdd
actions
JIRA URL: [SPARK-4094](https://issues.apache.org/jira/browse/SPARK-4094)
You can merge this pull request into
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2771#issuecomment-60555869
[Test build #22280 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22280/consoleFull)
for PR 2771 at commit
Github user gvramana commented on the pull request:
https://github.com/apache/spark/pull/2762#issuecomment-60556024
Yes, one more advantage of passing object inspector as parameter is,
constants need not be allocated every time, same value in
constantObjectInpector can be reused. I
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2956#issuecomment-60556120
[Test build #22281 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22281/consoleFull)
for PR 2956 at commit
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/2781#issuecomment-60556812
retest this please
---
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2685#issuecomment-60556909
Yeah, I like that idea.
On Oct 26, 2014 8:43 PM, wangfei notificati...@github.com wrote:
@marmbrus https://github.com/marmbrus, how about make a new sub
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2753#issuecomment-60556908
[Test build #22275 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22275/consoleFull)
for PR 2753 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2753#issuecomment-60556917
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/2901#issuecomment-60556986
[Test build #22274 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22274/consoleFull)
for PR 2901 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2901#issuecomment-60556992
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/2922#issuecomment-60557108
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/2922#issuecomment-60557102
[Test build #22277 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22277/consoleFull)
for PR 2922 at commit
Github user scwf commented on the pull request:
https://github.com/apache/spark/pull/2884#issuecomment-60557917
retest this please
---
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/2954#issuecomment-60558127
[Test build #22278 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22278/consoleFull)
for PR 2954 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2954#issuecomment-60558131
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/2771#issuecomment-60558681
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/2771#issuecomment-60558676
[Test build #22280 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22280/consoleFull)
for PR 2771 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2955#issuecomment-60558850
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/2955#issuecomment-60558845
[Test build #22279 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22279/consoleFull)
for PR 2955 at commit
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/2956#discussion_r19391269
--- Diff: core/src/main/scala/org/apache/spark/rdd/RDD.scala ---
@@ -1204,6 +1204,8 @@ abstract class RDD[T: ClassTag](
} else if
Github user WangTaoTheTonic commented on the pull request:
https://github.com/apache/spark/pull/2955#issuecomment-60558978
Jenkins, test this please.
---
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
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/2955#issuecomment-60559230
It seems much more desirable to just support 3g or 200m in this
argument, as was intended. `Utils.memoryStringToMb` can do the conversion.
---
If your project is set up
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2955#issuecomment-60559246
[Test build #22282 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22282/consoleFull)
for PR 2955 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/2846#issuecomment-60559452
The `awk` command here is still a little wrong, as it matches any string
`error`. `grep \[error\]` definitely works on `scalastyle.txt` to match
`[error]`. There's a
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/2685#issuecomment-60559682
Sorry, are we going to support both Hive 0.12 0.13.1 in long term? I am
working on SerDe stuff #2570, seems lots of method signatures changed after
upgrading to
Github user WangTaoTheTonic commented on the pull request:
https://github.com/apache/spark/pull/2955#issuecomment-60559959
@srowen I thought this way at beginning, but after more dig I found in
`ClientBase.scala` there is an initilization of `ApplicationMaster` using
arguments from
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2570#issuecomment-60560204
[Test build #22283 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22283/consoleFull)
for PR 2570 at commit
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/2570#issuecomment-60560261
@marmbrus, I've rebase dthe code with latest master (with Hive 0.13.1
supported, but not compatible with Hive 0.12). Please let me know if you have
concerns on
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2570#issuecomment-60560430
[Test build #22283 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22283/consoleFull)
for PR 2570 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2570#issuecomment-60560431
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/2956#issuecomment-60560699
[Test build #22281 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22281/consoleFull)
for PR 2956 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2956#issuecomment-60560702
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
GitHub user zsxwing opened a pull request:
https://github.com/apache/spark/pull/2957
[SPARK-4097] Fix the race condition of 'thread'
There is a chance that `thread` is null when calling `thread.interrupt()`.
```Scala
override def cancel(): Unit = this.synchronized {
Github user sarutak commented on a diff in the pull request:
https://github.com/apache/spark/pull/2939#discussion_r19392124
--- Diff: sql/core/src/test/scala/org/apache/spark/sql/SQLQuerySuite.scala
---
@@ -556,6 +556,8 @@ class SQLQuerySuite extends QueryTest with
Github user sarutak commented on a diff in the pull request:
https://github.com/apache/spark/pull/2939#discussion_r19392140
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/RangeJoins.scala ---
@@ -0,0 +1,83 @@
+/*
+ * Licensed to the Apache Software
Github user sarutak commented on a diff in the pull request:
https://github.com/apache/spark/pull/2939#discussion_r19392150
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/RangeJoins.scala ---
@@ -0,0 +1,83 @@
+/*
+ * Licensed to the Apache Software
Github user sarutak commented on a diff in the pull request:
https://github.com/apache/spark/pull/2939#discussion_r19392165
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/RangeJoinImpl.scala ---
@@ -0,0 +1,64 @@
+/*
+ * Licensed to the Apache Software
Github user sarutak commented on a diff in the pull request:
https://github.com/apache/spark/pull/2939#discussion_r19392161
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/RangeJoinImpl.scala ---
@@ -0,0 +1,64 @@
+/*
+ * Licensed to the Apache Software
Github user sarutak commented on a diff in the pull request:
https://github.com/apache/spark/pull/2939#discussion_r19392217
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/SqlParser.scala ---
@@ -188,8 +191,18 @@ class SqlParser extends AbstractSparkSQLParser {
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2957#issuecomment-60561668
[Test build #22284 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22284/consoleFull)
for PR 2957 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2607#issuecomment-60561667
[Test build #22285 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22285/consoleFull)
for PR 2607 at commit
Github user sarutak commented on a diff in the pull request:
https://github.com/apache/spark/pull/2939#discussion_r19392262
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/RangeJoinImpl.scala ---
@@ -0,0 +1,64 @@
+/*
+ * Licensed to the Apache Software
Github user sarutak commented on a diff in the pull request:
https://github.com/apache/spark/pull/2939#discussion_r19392296
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/RangeJoins.scala ---
@@ -0,0 +1,83 @@
+/*
+ * Licensed to the Apache Software
Github user sarutak commented on a diff in the pull request:
https://github.com/apache/spark/pull/2939#discussion_r19392285
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/RangeJoins.scala ---
@@ -0,0 +1,83 @@
+/*
+ * Licensed to the Apache Software
Github user sarutak commented on a diff in the pull request:
https://github.com/apache/spark/pull/2939#discussion_r19392318
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/RangeJoins.scala ---
@@ -0,0 +1,83 @@
+/*
+ * Licensed to the Apache Software
Github user sarutak commented on a diff in the pull request:
https://github.com/apache/spark/pull/2939#discussion_r19392340
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkStrategies.scala ---
@@ -102,6 +102,13 @@ private[sql] abstract class SparkStrategies
Github user sarutak commented on a diff in the pull request:
https://github.com/apache/spark/pull/2939#discussion_r19392360
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/SQLRangeJoinSuite.scala
---
@@ -0,0 +1,81 @@
+/**
+ * Licensed to Big Data Genomics
Github user sarutak commented on a diff in the pull request:
https://github.com/apache/spark/pull/2939#discussion_r19392347
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/SQLRangeJoinSuite.scala
---
@@ -0,0 +1,81 @@
+/**
+ * Licensed to Big Data Genomics
Github user sarutak commented on a diff in the pull request:
https://github.com/apache/spark/pull/2939#discussion_r19392368
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/SQLRangeJoinSuite.scala
---
@@ -0,0 +1,81 @@
+/**
+ * Licensed to Big Data Genomics
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2884#issuecomment-60562034
[Test build #473 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/473/consoleFull)
for PR 2884 at commit
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/2615#issuecomment-60562052
@pwendell I tried your reproducer after changing a few things, so I am not
sure whether I fixed it accidentally or I could not reproduce at all.
---
If your project
GitHub user WangTaoTheTonic opened a pull request:
https://github.com/apache/spark/pull/2958
[SPARK-4098][YARN]use appUIAddress instead of appUIHostPort in yarn-client
mode
https://issues.apache.org/jira/browse/SPARK-4098
You can merge this pull request into a Git repository by
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/2570#issuecomment-60562071
Build failed because this PR is only compatible with Hive 0,13.1 (not 0.12
any more).
---
If your project is set up for it, you can reply to this email and have
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/2939#issuecomment-60562141
Hi @kozanitis , did you try to run sbt/sbt -Phive scalastyle ?
That command helps you, telling which code is invalid style.
Maybe, the length of some lines is over
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2615#issuecomment-60562506
[Test build #22287 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22287/consoleFull)
for PR 2615 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2958#issuecomment-60562505
[Test build #22286 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22286/consoleFull)
for PR 2958 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2884#issuecomment-60562729
[Test build #473 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/473/consoleFull)
for PR 2884 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2615#issuecomment-60562791
[Test build #22287 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22287/consoleFull)
for PR 2615 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2615#issuecomment-60562793
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user jongyoul commented on the pull request:
https://github.com/apache/spark/pull/2126#issuecomment-60563727
@andrewor14 You mean that a clean way to merge this patch into main stream
is that I code this patch from current master branch and make a pull requst
again, isn't it?
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/2957#issuecomment-60563934
You can also just take a local reference to the thread, and operate on it.
The local reference will of course be null in both cases or not-null in both
cases.
---
If
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/2955#issuecomment-60564242
Hm, how do you mean? the rest of the code already expects this to be an
`Int` and a number of megabytes. Nothing else can be further parsing this (or
else that's a bug).
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2955#issuecomment-60564958
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/2955#issuecomment-60564950
[Test build #22282 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22282/consoleFull)
for PR 2955 at commit
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/2957#issuecomment-60565342
You can also just take a local reference to the thread, and operate on
it. The local reference will of course be null in both cases or not-null in
both cases.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2957#issuecomment-60565582
[Test build #22289 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22289/consoleFull)
for PR 2957 at commit
Github user WangTaoTheTonic commented on the pull request:
https://github.com/apache/spark/pull/2955#issuecomment-60566095
Guess I didn't make it clear. So I paste some code segment to help. Excuse
me for this.
In ClientBase.scala we could see:
` val amClass =
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2906#issuecomment-60566259
[Test build #22290 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22290/consoleFull)
for PR 2906 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2906#issuecomment-60566367
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/2906#issuecomment-60566364
[Test build #22290 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22290/consoleFull)
for PR 2906 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2957#issuecomment-60566474
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/2906#issuecomment-60566674
@mengxr thank you for your feedback.
Is there a paper that you used as reference? If so, please cite it in the
doc.
Yes. I added the comment into the doc.
Github user WangTaoTheTonic commented on the pull request:
https://github.com/apache/spark/pull/2958#issuecomment-60567168
Same replacement happened in https://github.com/apache/spark/pull/2276,
same change in `runExecutorLauncher` is mentioned in that PR but done nothing.
---
If
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2906#issuecomment-60567740
[Test build #22291 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22291/consoleFull)
for PR 2906 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2607#issuecomment-60568456
[Test build #22285 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22285/consoleFull)
for PR 2607 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2607#issuecomment-60568462
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/2957#issuecomment-60568910
[Test build #22284 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22284/consoleFull)
for PR 2957 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2957#issuecomment-60568924
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/2878#issuecomment-60569271
[Test build #22292 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22292/consoleFull)
for PR 2878 at commit
1 - 100 of 518 matches
Mail list logo
