Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6767#issuecomment-158827317
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/6767#issuecomment-158827315
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 cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/9840#discussion_r45569682
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/ScalaReflection.scala
---
@@ -124,17 +124,46 @@ object ScalaReflection extends
GitHub user yanboliang opened a pull request:
https://github.com/apache/spark/pull/9897
[SPARK-11912] [ML] ml.feature.PCA minor refactor
Like [SPARK-11852](https://issues.apache.org/jira/browse/SPARK-11852),
```k``` is params and we should save it under ```metadata/``` rather than
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9900#issuecomment-158853714
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/9873#issuecomment-158857689
Merged into master and branch-1.6.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9898#issuecomment-158857692
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/9898#issuecomment-158857690
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/9873
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/9885
---
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/9899#issuecomment-158859749
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/9885#issuecomment-158859845
Merged into master and branch-1.6. Thanks!
---
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/9902#issuecomment-158862948
**[Test build #46512 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46512/consoleFull)**
for PR 9902 at commit
Github user jbonofre commented on the pull request:
https://github.com/apache/spark/pull/9860#issuecomment-158863908
PR rebased and updated to use a button instead of a checkbox.
---
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/9903#issuecomment-158866811
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/9903#issuecomment-158866808
**[Test build #46513 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46513/consoleFull)**
for PR 9903 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9903#issuecomment-158866768
**[Test build #46513 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46513/consoleFull)**
for PR 9903 at commit
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/9904#issuecomment-158867919
That is great! You fixed the bug! Thank you very much!
---
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/9903#issuecomment-158872213
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/9903#issuecomment-158872214
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/9898#issuecomment-158857640
**[Test build #46506 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46506/consoleFull)**
for PR 9898 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9848
---
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/9894#issuecomment-158858912
LGTM. Merged into master and branch-1.6. Thanks!
---
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 navis commented on the pull request:
https://github.com/apache/spark/pull/6767#issuecomment-158858838
@chenghao-intel Sorry for long delay. Could see this again when your time
allowed?
---
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/9897
---
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/9897#issuecomment-158858931
LGTM. Merged into master and branch-1.6. Thanks!
---
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 adrian-wang opened a pull request:
https://github.com/apache/spark/pull/9902
[SPARK-11916][SQL]Expression TRIM/LTRIM/RTRIM to support specific trim word
supports expressions like `trim('xxxabcxxx', 'x')`
You can merge this pull request into a Git repository by running:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8714#issuecomment-158871116
**[Test build #46516 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46516/consoleFull)**
for PR 8714 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9903#issuecomment-158872139
**[Test build #46515 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46515/consoleFull)**
for PR 9903 at commit
GitHub user zjffdu opened a pull request:
https://github.com/apache/spark/pull/9901
[SPARK-11860][PYSAPRK][DOCUMENTATION] Invalid argument specification â¦
â¦for registerFunction [Python]
Straightforward change on the python doc
You can merge this pull request into a Git
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9826
---
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/9826#issuecomment-158858659
LGTM. Merged into master and branch-1.6. Thanks! (The Jenkins test failure
is irrelevant. The PR build doesn't compile doc anyway. So I verified the
changes on my local
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9901#issuecomment-158859254
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/9883#issuecomment-158859349
**[Test build #46509 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46509/consoleFull)**
for PR 9883 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9901#issuecomment-158859253
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/9901#issuecomment-158859096
**[Test build #46511 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46511/consoleFull)**
for PR 9901 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9883#issuecomment-158859505
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/8714#issuecomment-158859608
Hi @andrewor14 , from the code that `worker` never set the state to
`RUNNING`, currently when executor is started, `worker` will set the executor
state to `LAUNCHING`
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9899#issuecomment-158859716
**[Test build #46507 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46507/consoleFull)**
for PR 9899 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9883#issuecomment-158859506
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/9899#issuecomment-158859750
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
GitHub user zjffdu opened a pull request:
https://github.com/apache/spark/pull/9903
[SPARK-11917][PYSPARK] Add SQLContext#dropTempTable to PySpark
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zjffdu/spark SPARK-11917
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9903#issuecomment-158866809
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 dilipbiswal commented on the pull request:
https://github.com/apache/spark/pull/9844#issuecomment-158869241
Thanks a lot @cloud-fan. Actually i do remember trying to do something
similar. So i had tried to filter on resolved and was trying to only pick
un-resolved
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/9844#issuecomment-158870885
how about this:
```
val unresolvedSortOrders = sortOrders.filterNot(_.resolved)
val resolvedSortOrders = ... // the original logic that copy to aggregate
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8714#issuecomment-158871764
**[Test build #46517 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46517/consoleFull)**
for PR 8714 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9901#issuecomment-158857060
**[Test build #46511 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46511/consoleFull)**
for PR 9901 at commit
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/9848#issuecomment-158858117
LGTM. Merged into master and branch-1.6. Thanks!
---
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/9889#issuecomment-158860840
**[Test build #46510 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46510/consoleFull)**
for PR 9889 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9889#issuecomment-158860880
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/9889#issuecomment-158860879
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 cloud-fan opened a pull request:
https://github.com/apache/spark/pull/9904
[SPARK-11894][SQL] fix isNull for GetInternalRowField
We should use `InternalRow.isNullAt` to check if the field is null before
calling `InternalRow.getXXX`
Thanks @gatorsmile who
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9904#issuecomment-158869426
**[Test build #46514 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46514/consoleFull)**
for PR 9904 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9903#issuecomment-158869339
**[Test build #46515 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46515/consoleFull)**
for PR 9903 at commit
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/8714#issuecomment-158871565
Hi @andrewor14 , please help to take a look at this update, not sure is
this what you want. Thanks a lot.
---
If your project is set up for it, you can reply to this
Github user dilipbiswal commented on the pull request:
https://github.com/apache/spark/pull/9844#issuecomment-158871599
@cloud-fan Wow.. thank you very much. I will try it. Thanks again,
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9264#issuecomment-158817738
**[Test build #46499 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46499/consoleFull)**
for PR 9264 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6767#issuecomment-158827313
**[Test build #46501 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46501/consoleFull)**
for PR 6767 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6767#issuecomment-158826957
**[Test build #46501 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46501/consoleFull)**
for PR 6767 at commit
Github user yanboliang commented on the pull request:
https://github.com/apache/spark/pull/9807#issuecomment-158846302
cc @jkbradley
---
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/9898#issuecomment-158846179
**[Test build #46506 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46506/consoleFull)**
for PR 9898 at commit
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/9844#issuecomment-158846201
In
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9897#issuecomment-158847450
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/9897#issuecomment-158847410
**[Test build #46505 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46505/consoleFull)**
for PR 9897 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9897#issuecomment-158847452
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/9900#issuecomment-158851504
**[Test build #46508 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46508/consoleFull)**
for PR 9900 at commit
GitHub user saurfang opened a pull request:
https://github.com/apache/spark/pull/9896
[SPARK-11906][Web UI] Speculation Tasks Cause ProgressBar UI Overflow
When there are speculative tasks in the stage, running progress bar could
overflow and goes hidden on a new line:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9883#issuecomment-158827710
**[Test build #46502 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46502/consoleFull)**
for PR 9883 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9612#issuecomment-158835715
**[Test build #46504 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46504/consoleFull)**
for PR 9612 at commit
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/9883#discussion_r45571748
--- Diff: sql/catalyst/src/main/scala/org/apache/spark/sql/Row.scala ---
@@ -424,16 +424,34 @@ trait Row extends Serializable {
true
}
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9889#issuecomment-158851741
**[Test build #46510 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46510/consoleFull)**
for PR 9889 at commit
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/9889#issuecomment-158851730
@marmbrus Do these newly added test cases resolve your concerns?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9900#issuecomment-158853676
**[Test build #46508 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46508/consoleFull)**
for PR 9900 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9900#issuecomment-158853713
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/9896#issuecomment-158817345
**[Test build #46500 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46500/consoleFull)**
for PR 9896 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9873#issuecomment-158824419
**[Test build #2096 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2096/consoleFull)**
for PR 9873 at commit
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/9883#issuecomment-158826613
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 cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/9612#issuecomment-158832674
cc @yhuai
---
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 cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/9612#issuecomment-158832635
ok to test
---
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 viirya opened a pull request:
https://github.com/apache/spark/pull/9900
[SPARK-11915][SQL] Fix flaky python test pyspark.sql.group
JIRA: https://issues.apache.org/jira/browse/SPARK-11915
We should sort the aggregation results to make the test stable.
You can
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9612#issuecomment-158853327
**[Test build #46504 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46504/consoleFull)**
for PR 9612 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9612#issuecomment-158853383
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/9612#issuecomment-158853382
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/9264#issuecomment-158817770
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/9264#issuecomment-158817771
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/9878#discussion_r45568460
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/feature/Word2Vec.scala ---
@@ -315,13 +315,15 @@ class Word2Vec extends Serializable with Logging {
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/9878#discussion_r45568476
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/feature/Word2Vec.scala ---
@@ -315,13 +315,15 @@ class Word2Vec extends Serializable with Logging {
Github user dilipbiswal commented on the pull request:
https://github.com/apache/spark/pull/9844#issuecomment-158837039
@cloud-fan Thank you for the explanation as always. Trying to see if i
understood your suggestion properly. Were you suggesting to add another case
under
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9897#issuecomment-158839770
**[Test build #46505 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46505/consoleFull)**
for PR 9897 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9899#issuecomment-158847634
**[Test build #46507 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46507/consoleFull)**
for PR 9899 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9896#issuecomment-158822966
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/9896#issuecomment-158822951
**[Test build #46500 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46500/consoleFull)**
for PR 9896 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9896#issuecomment-158822965
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/6767#issuecomment-158828057
**[Test build #46503 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46503/consoleFull)**
for PR 6767 at commit
GitHub user cloud-fan opened a pull request:
https://github.com/apache/spark/pull/9898
[SPARK-11913][SQL] support typed aggregate for complex buffer schema
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cloud-fan/spark agg
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9883#issuecomment-158851369
**[Test build #46509 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46509/consoleFull)**
for PR 9883 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9264#issuecomment-158817052
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/9264#issuecomment-158817053
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/9264#issuecomment-158817011
**[Test build #46498 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46498/consoleFull)**
for PR 9264 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9873#issuecomment-158825466
**[Test build #2096 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2096/consoleFull)**
for PR 9873 at commit
1 - 100 of 187 matches
Mail list logo
