Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12346#issuecomment-209195998
**[Test build #55679 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55679/consoleFull)**
for PR 12346 at commit
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/12346#issuecomment-209195738
cc @marmbrus
---
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 opened a pull request:
https://github.com/apache/spark/pull/12346
[SPARK-14554][SQL][follow-up] use checkDataset to check the result
## What changes were proposed in this pull request?
address this comment:
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/12326#issuecomment-209195204
@cloud-fan Could you please take a look?
---
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/12271#issuecomment-209194477
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/12271#issuecomment-209194478
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/12271#issuecomment-209194377
**[Test build #55674 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55674/consoleFull)**
for PR 12271 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12340#issuecomment-209193831
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/12340#issuecomment-209193832
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/12340#issuecomment-209193710
**[Test build #55671 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55671/consoleFull)**
for PR 12340 at commit
Github user avulanov commented on the pull request:
https://github.com/apache/spark/pull/10806#issuecomment-209193632
Good point. According to matrices multiplication benchmark, we can get peak
performance on modern CPUs with square matrices somewhere between 4Kx4K and
8Kx8K. So, it
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12345#issuecomment-209192126
**[Test build #55678 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55678/consoleFull)**
for PR 12345 at commit
Github user sameeragarwal closed the pull request at:
https://github.com/apache/spark/pull/12224
---
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
Github user sameeragarwal commented on the pull request:
https://github.com/apache/spark/pull/12345#issuecomment-209190745
cc @nongli
---
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/12345#issuecomment-209190140
**[Test build #55677 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55677/consoleFull)**
for PR 12345 at commit
Github user sameeragarwal commented on the pull request:
https://github.com/apache/spark/pull/12345#issuecomment-209190135
Generate code for a query of the form `sqlContext.range(N).selectExpr("(id
& 65535) as k").groupBy("k").sum().collect()` looks like:
```java
/* 009
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12336#issuecomment-209189333
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/12336#issuecomment-209189330
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 sameeragarwal opened a pull request:
https://github.com/apache/spark/pull/12345
[SPARK-14447][SQL] Speed up TungstenAggregate w/ keys using AggregateHashMap
## What changes were proposed in this pull request?
This patch speeds up group-by aggregates by around
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12336#issuecomment-209188744
**[Test build #55669 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55669/consoleFull)**
for PR 12336 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12194#issuecomment-209187311
**[Test build #55676 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55676/consoleFull)**
for PR 12194 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12254#issuecomment-209187159
**[Test build #2782 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2782/consoleFull)**
for PR 12254 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12344#issuecomment-209185845
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/12344#issuecomment-209185837
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 tejasapatil commented on the pull request:
https://github.com/apache/spark/pull/12194#issuecomment-209185057
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12344#issuecomment-209185043
**[Test build #55670 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55670/consoleFull)**
for PR 12344 at commit
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/12254#issuecomment-209184280
LGTM
I'll rerun tests before merging
Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12254#issuecomment-209184327
**[Test build #2782 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2782/consoleFull)**
for PR 12254 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12224#issuecomment-209180095
**[Test build #55675 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55675/consoleFull)**
for PR 12224 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9440#issuecomment-209173348
[Test build #2781 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2781/console)
for PR 9440 at commit
Github user yjshen closed the pull request at:
https://github.com/apache/spark/pull/8224
---
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/9440#issuecomment-209172874
[Test build #2781 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2781/consoleFull)
for PR 9440 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12271#issuecomment-209172735
**[Test build #55674 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55674/consoleFull)**
for PR 12271 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/12271#issuecomment-209172015
I've ignored some tests in `HiveCompatibilitySuite` for now. I'll have a
look at them shortly. I just wanted to see if the rest of the tests will pass.
---
If your
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/11793#issuecomment-209171051
It looks like [https://github.com/apache/spark/pull/12039] solved this.
Can you please verify and close this PR if so? Thanks!
---
If your project is set up for
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/11917#issuecomment-209170349
Looks good, with just a few 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
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/11917#discussion_r59479210
--- Diff: examples/src/main/python/ml/count_vectorizer_example.py ---
@@ -0,0 +1,45 @@
+#
+# Licensed to the Apache Software Foundation (ASF) under
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/11917#discussion_r59479213
--- Diff: examples/src/main/python/ml/count_vectorizer_example.py ---
@@ -0,0 +1,45 @@
+#
+# Licensed to the Apache Software Foundation (ASF) under
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12271#issuecomment-209169942
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/12271#issuecomment-209169944
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/12271#issuecomment-209169833
**[Test build #55666 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55666/consoleFull)**
for PR 12271 at commit
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/11917#issuecomment-209169658
I can take a look
---
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/12343#issuecomment-209168664
**[Test build #55673 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55673/consoleFull)**
for PR 12343 at commit
Github user thunterdb commented on a diff in the pull request:
https://github.com/apache/spark/pull/12331#discussion_r59478228
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/classification/LogisticRegression.scala
---
@@ -273,6 +273,10 @@ class LogisticRegression
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/10664#issuecomment-209167374
This looks good; I just had 1 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
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/10664#discussion_r59477902
--- Diff:
mllib/src/test/scala/org/apache/spark/mllib/fpm/PrefixSpanSuite.scala ---
@@ -357,6 +358,39 @@ class PrefixSpanSuite extends SparkFunSuite with
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12343#issuecomment-209166279
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/12343#issuecomment-209166271
**[Test build #55672 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55672/consoleFull)**
for PR 12343 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12343#issuecomment-209166280
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/12343#issuecomment-209165641
**[Test build #55672 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55672/consoleFull)**
for PR 12343 at commit
Github user ericl commented on the pull request:
https://github.com/apache/spark/pull/12343#issuecomment-209165571
Oops, let's try that again
---
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 yhuai commented on the pull request:
https://github.com/apache/spark/pull/12343#issuecomment-209165475
oh, seems failed style check.
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/12339
---
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/12340#issuecomment-209164856
**[Test build #55671 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55671/consoleFull)**
for PR 12340 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12344#issuecomment-209164854
**[Test build #55670 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55670/consoleFull)**
for PR 12344 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12339#issuecomment-209164374
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/12339#issuecomment-209164476
Thanks, merging 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12339#issuecomment-209164372
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 davies opened a pull request:
https://github.com/apache/spark/pull/12344
[SPARK-14582] [SQL] increase paralleism for small tables
## What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
## How was this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12342#issuecomment-209164134
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/12342#issuecomment-209164137
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/12342#issuecomment-209164021
**[Test build #55663 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55663/consoleFull)**
for PR 12342 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12339#issuecomment-209164088
**[Test build #55659 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55659/consoleFull)**
for PR 12339 at commit
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/12327#issuecomment-209163845
cc @andrewor14
---
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/12338
---
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/12336#issuecomment-209163487
**[Test build #55669 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55669/consoleFull)**
for PR 12336 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12342#issuecomment-209162975
Test FAILed.
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/10664#issuecomment-209163149
Taking a look 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 have this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12342#issuecomment-209162971
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 davies commented on the pull request:
https://github.com/apache/spark/pull/12338#issuecomment-209162808
This is used for non-whole-stage codegen, also MapObjects does not support
interpret mode, or it's better to fallback. Class member may prevent JIT
compiler to do more
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12342#issuecomment-209162587
**[Test build #55662 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55662/consoleFull)**
for PR 12342 at commit
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/12338#issuecomment-209158443
One more question, actually there are some more places that we use local
variables as the input for expressions, e.g. `CodeGenContext.currentVars` in
whole stage
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12271#issuecomment-209158268
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/12271#issuecomment-209158146
**[Test build #55658 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55658/consoleFull)**
for PR 12271 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12271#issuecomment-209158266
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 the pull request:
https://github.com/apache/spark/pull/12338#issuecomment-209157698
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12340#issuecomment-209157468
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/12340#issuecomment-209157469
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/12340#issuecomment-209157343
**[Test build #55657 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55657/consoleFull)**
for PR 12340 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12334#issuecomment-209156854
**[Test build #55668 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55668/consoleFull)**
for PR 12334 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/12334#issuecomment-209155625
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12343#issuecomment-209155212
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/12343#issuecomment-209155216
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/12343#issuecomment-209155210
**[Test build #55667 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55667/consoleFull)**
for PR 12343 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12343#issuecomment-209154880
**[Test build #55667 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55667/consoleFull)**
for PR 12343 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12334#issuecomment-209154695
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/12334#issuecomment-209154693
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/12334#issuecomment-209154378
**[Test build #55650 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55650/consoleFull)**
for PR 12334 at commit
GitHub user ericl opened a pull request:
https://github.com/apache/spark/pull/12343
[TEST] Test cherry-pick of a commit into branch 1.6
This is just to use the jenkins builder, and should not be merged. cc
@yhuai
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/12271#issuecomment-209153212
**[Test build #55666 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55666/consoleFull)**
for PR 12271 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12304#issuecomment-209153101
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/12304#issuecomment-209152803
**[Test build #55665 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55665/consoleFull)**
for PR 12304 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12304#issuecomment-209153105
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/12304#issuecomment-209150350
**[Test build #55665 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55665/consoleFull)**
for PR 12304 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12338#issuecomment-209148818
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/12334#issuecomment-209148782
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/12338#issuecomment-209148819
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/12334#issuecomment-209148784
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/12338#issuecomment-209148539
**[Test build #55651 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55651/consoleFull)**
for PR 12338 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12334#issuecomment-209148425
**[Test build #55647 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55647/consoleFull)**
for PR 12334 at commit
101 - 200 of 740 matches
Mail list logo
