Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/5149#issuecomment-94650812
Okay I'll pull this in now.
---
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/3062#issuecomment-94655050
@selvinsource Thanks! There are some indentation issues in my PR. Could you
help fix it?
The latest version of `jpmml-model` requires Java 7 or newer, while Spark
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/5570
---
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/5603#issuecomment-94651444
[Test build #30642 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30642/consoleFull)
for PR 5603 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3753#issuecomment-94653252
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/3753#issuecomment-94653249
[Test build #30645 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30645/consoleFull)
for PR 3753 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5542#issuecomment-94653175
[Test build #30644 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30644/consoleFull)
for PR 5542 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4380#issuecomment-94654683
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/5455#issuecomment-94656053
@MechCoder I'm not an expert here, but I'll ask around. I'm wondering if
the failure in PythonMLLibAPISuite indicates that the issue is with the tuple
(or tuple
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5270#issuecomment-94656142
[Test build #30635 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30635/consoleFull)
for PR 5270 at commit
Github user scwf commented on the pull request:
https://github.com/apache/spark/pull/4380#issuecomment-94666147
Updated, to summarize this:
1 Get a unresolved plan WriteToDirectory(path, child, isLocal, extra:
ASTNode) in hiveql
2 Analyze WriteToDirectory(path: String,
Github user DoingDone9 closed the pull request at:
https://github.com/apache/spark/pull/5418
---
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/5604#issuecomment-9449
[Test build #30652 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30652/consoleFull)
for PR 5604 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/5595#issuecomment-94652273
Can you create a PR to update documentation?
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5604#issuecomment-94652284
[Test build #30643 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30643/consoleFull)
for PR 5604 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/5595#issuecomment-94652262
Merging in master. 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 project does not have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5247#issuecomment-94654202
[Test build #30632 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30632/consoleFull)
for PR 5247 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5247#issuecomment-94654211
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/5604#issuecomment-94655851
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/5604#issuecomment-94655848
[Test build #30649 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30649/consoleFull)
for PR 5604 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5574#issuecomment-94657281
**[Test build #30631 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30631/consoleFull)**
for PR 5574 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5574#issuecomment-94657310
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/4015#issuecomment-94662954
[Test build #30636 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30636/consoleFull)
for PR 4015 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4015#issuecomment-94662960
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user mce commented on the pull request:
https://github.com/apache/spark/pull/5439#issuecomment-94652390
@cfregly any other comments?
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5604#issuecomment-94652415
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/5595
---
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/5604#issuecomment-94652412
[Test build #30643 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30643/consoleFull)
for PR 5604 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5601#issuecomment-94654251
[Test build #30647 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30647/consoleFull)
for PR 5601 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3753#issuecomment-94654237
[Test build #30648 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30648/consoleFull)
for PR 3753 at commit
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/5455#discussion_r28754622
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/api/python/PythonMLLibAPI.scala ---
@@ -985,6 +985,7 @@ private[spark] object SerDe extends Serializable
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/5455#discussion_r28754624
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/api/python/PythonMLLibAPI.scala ---
@@ -994,19 +995,22 @@ private[spark] object SerDe extends
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/5605#issuecomment-94662155
Note that this simply brings https://github.com/apache/spark/pull/5427 up
to date.
---
If your project is set up for it, you can reply to this email and have your
reply
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/5605
[SPARK-6953] [PySpark] speed up python tests
This PR try to speed up some python tests:
```
tests.py144s - 103s -41s
mllib/classification.py 24s - 17s
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/5149#issuecomment-94651348
Ah actually looks like there is a small bug caused by the refactoring (ping
@texasmichelle):
```
Traceback (most recent call last):
File
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/5604#issuecomment-94651361
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5604#issuecomment-94651277
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3062#issuecomment-94653600
[Test build #30646 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30646/consoleFull)
for PR 3062 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5605#issuecomment-94663901
[Test build #30651 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30651/consoleFull)
for PR 5605 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4688#issuecomment-94649685
[Test build #30641 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30641/consoleFull)
for PR 4688 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5604#issuecomment-94655371
[Test build #30649 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30649/consoleFull)
for PR 5604 at commit
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/5270#issuecomment-94662381
Merged into master. 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 project does not have
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/5427#issuecomment-94662257
I brought this up to date at https://github.com/apache/spark/pull/5605
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/5270
---
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/3753#issuecomment-94653107
[Test build #30645 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30645/consoleFull)
for PR 3753 at commit
Github user DoingDone9 commented on a diff in the pull request:
https://github.com/apache/spark/pull/5538#discussion_r28751859
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/sqlUDFCurrentDB.scala ---
@@ -0,0 +1,43 @@
+/*
+ * Licensed to the Apache Software
GitHub user guowei2 opened a pull request:
https://github.com/apache/spark/pull/5604
[SPARK-1442][SQL][WIP] Window Function Support for Spart SQL
The PR is WIP now for NPE when generating golden answer
You can merge this pull request into a Git repository by running:
$ git
Github user selvinsource commented on the pull request:
https://github.com/apache/spark/pull/3062#issuecomment-94653680
@mengxr I merged your PR, I will review the libraries and let you know.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/5427#issuecomment-94661874
MLlib changes look good to me.
---
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/5270#issuecomment-94656150
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user vruusmann commented on the pull request:
https://github.com/apache/spark/pull/3062#issuecomment-94661002
@mengxr Branches 1.0.X and 1.1.X are Java 6. The new branch 1.2.X is Java 7.
The latest Java 6 compatible version is 1.1.15.
---
If your project is set up for
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/5570#issuecomment-94661265
Thanks. I'm going to merge this in 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5604#issuecomment-94661415
[Test build #30650 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30650/consoleFull)
for PR 5604 at commit
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/5607#discussion_r28801849
--- Diff: docs/configuration.md ---
@@ -982,6 +982,34 @@ Apart from these, the following properties are also
available, and may be useful
This is only
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/5607#discussion_r28801842
--- Diff: docs/configuration.md ---
@@ -982,6 +982,34 @@ Apart from these, the following properties are also
available, and may be useful
This is only
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5533#issuecomment-94894427
[Test build #30680 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30680/consoleFull)
for PR 5533 at commit
GitHub user brkyvz opened a pull request:
https://github.com/apache/spark/pull/5616
[SPARK-6829] Added math functions for DataFrames
Implemented code-gen and functions for almost all math functions found in
scala.math (max, min and abs were already present).
cc @mengxr
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/5403#issuecomment-94905121
My two cents: I think the main reason to merge this is that one doesn't
need to maintain patches out of tree that'll become outdated when the interface
changes :) Also
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5616#issuecomment-94913337
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/5618#issuecomment-94916039
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/5607#issuecomment-94880443
Can you also change the default timeout? 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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5533#issuecomment-94894459
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/5615#issuecomment-94899437
[Test build #30685 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30685/consoleFull)
for PR 5615 at commit
Github user sryza commented on the pull request:
https://github.com/apache/spark/pull/5536#issuecomment-94915882
Thanks for putting together those graphs Cheolsoo. I think they're really
helpful for thinking about this.
The side effect that I'm worried about is
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5467#issuecomment-94917585
[Test build #30689 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30689/consoleFull)
for PR 5467 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5606#issuecomment-94878007
[Test build #30681 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30681/consoleFull)
for PR 5606 at commit
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/5455#discussion_r28801082
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/api/python/PythonMLLibAPI.scala ---
@@ -994,19 +996,22 @@ private[spark] object SerDe extends
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5574#issuecomment-94878949
**[Test build #30677 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30677/consoleFull)**
for PR 5574 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5574#issuecomment-94878964
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/5607#discussion_r28800959
--- Diff: docs/configuration.md ---
@@ -982,6 +982,34 @@ Apart from these, the following properties are also
available, and may be useful
This is
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/5455#issuecomment-94878936
LGTM except one minor inline comment.
---
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/5606#issuecomment-94889898
As an example of the speedup that this can give, here's a simple benchmark.
Launch spark-shell with the following options:
```
./bin/spark-shell
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5606#issuecomment-94900422
[Test build #30686 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30686/consoleFull)
for PR 5606 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5615#issuecomment-94901979
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 have this feature
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5616#issuecomment-94907546
[Test build #30687 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30687/consoleFull)
for PR 5616 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5616#issuecomment-94907556
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/5616#issuecomment-94907488
[Test build #30687 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30687/consoleFull)
for PR 5616 at commit
Github user tnachen commented on the pull request:
https://github.com/apache/spark/pull/5597#issuecomment-94918952
It's logged each time we recover resources in Mesos since that's when we
evaluate when the filter should be applied. And yes Mesos needs a positive
value for refuse
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5574#issuecomment-94888456
[Test build #30683 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30683/consoleFull)
for PR 5574 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/4145
---
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 jkbradley commented on the pull request:
https://github.com/apache/spark/pull/5585#issuecomment-94895292
Closing this pending discussions
---
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/5606#issuecomment-94895158
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user jkbradley closed the pull request at:
https://github.com/apache/spark/pull/5585
---
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 vanzin opened a pull request:
https://github.com/apache/spark/pull/5615
[minor] [build] Set java options when generating mima ignores.
The default java options make the call to GenerateMIMAIgnore take
forever to run since it's gc'ing all the time. Improve things by
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/5606#issuecomment-94899383
Jenkins, 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2342#issuecomment-94901177
[Test build #30679 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30679/consoleFull)
for PR 2342 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2342#issuecomment-94901211
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5615#issuecomment-94912457
guess i forgot to log myself out of the amplab account. :)
lgtm!
---
If your project is set up for it, you can reply to this email and have your
reply
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5616#issuecomment-94913331
[Test build #30688 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30688/consoleFull)
for PR 5616 at commit
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/2342#issuecomment-94889476
If you want you can keep the stage view for now, but we may decide to
remove it before merging this patch.
---
If your project is set up for it, you can reply to this
Github user MechCoder commented on the pull request:
https://github.com/apache/spark/pull/5467#issuecomment-94917250
@jkbradley fixed, hopefully should be 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
Github user MechCoder commented on the pull request:
https://github.com/apache/spark/pull/5455#issuecomment-94880060
done
---
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
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5615#issuecomment-94900860
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 have this feature
enabled
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5455#issuecomment-94911157
[Test build #30682 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30682/consoleFull)
for PR 5455 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5455#issuecomment-94911167
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/5455#issuecomment-94880976
[Test build #30682 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30682/consoleFull)
for PR 5455 at commit
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/3913#issuecomment-94886124
Sure, sounds fine to me. We can have a static method for it.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/5467#discussion_r28805366
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/feature/Word2Vec.scala ---
@@ -429,7 +429,25 @@ class Word2Vec extends Serializable with Logging {
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/5467#discussion_r28805372
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/feature/Word2Vec.scala ---
@@ -479,9 +497,23 @@ class Word2VecModel private[mllib] (
*/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5567#issuecomment-94896888
[Test build #30684 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30684/consoleFull)
for PR 5567 at commit
1 - 100 of 588 matches
Mail list logo
