Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8688#issuecomment-139463274
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8688#issuecomment-139463302
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8713#issuecomment-139465728
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/8688#issuecomment-139463871
[Test build #42313 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42313/consoleFull)
for PR 8688 at commit
Github user zjffdu commented on the pull request:
https://github.com/apache/spark/pull/8688#issuecomment-139463912
Thanks for the review @vanzin
For SparkUI, yes it is not necessary to put appId in constructor. But for
history server, the appId is known when creating SparkUI.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8688#issuecomment-139465478
[Test build #42314 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42314/consoleFull)
for PR 8688 at commit
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8697#issuecomment-139465613
@y-shimizu The changes to `ml-ensembles` look good. But we also need to
update other `spark.ml` guides, e..g, `ml-features.md` and
`ml-linear-methods.md`. Please find
GitHub user maver1ck opened a pull request:
https://github.com/apache/spark/pull/8712
[SPARK-10559] DataFrame schema ArrayType should accept ResultIterable
Patch to repair it.
https://issues.apache.org/jira/browse/SPARK-10559
You can merge this pull request into a Git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8709#issuecomment-139465363
[Test build #1740 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1740/console)
for PR 8709 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8712#issuecomment-139463270
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8688#issuecomment-139464373
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/8698#issuecomment-139469937
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/8698#issuecomment-139469830
[Test build #42311 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42311/console)
for PR 8698 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8698#issuecomment-139469938
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/8688#issuecomment-139464963
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
GitHub user GavinGavinNo1 opened a pull request:
https://github.com/apache/spark/pull/8713
Update IsolatedClientLoader.scala
To resolve problem mentioned in SPARK-10529, I add an attribute of
ThreadLocal type in object IsolatedClientLoader. So, no matter
how many HiveContext
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8688#issuecomment-139464931
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7118#issuecomment-139460835
[Test build #42312 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42312/console)
for PR 7118 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8688#issuecomment-139464370
[Test build #42313 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42313/console)
for PR 8688 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8688#issuecomment-139464375
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/7118#issuecomment-139460868
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/7118#issuecomment-139460867
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/8604#issuecomment-139589897
[Test build #42341 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42341/consoleFull)
for PR 8604 at commit
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/8687#discussion_r39291942
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/execution/InsertIntoHiveTable.scala
---
@@ -178,6 +178,13 @@ case class InsertIntoHiveTable(
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8700#issuecomment-139602565
@smartkiwi Sorry, my comments duplicate @davies 's ...
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/8701#issuecomment-139602585
@tgravescs could you close this? I don't think it's closed automatically
since it's in a branch. Thanks!
---
If your project is set up for it, you can reply to this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8719#issuecomment-139611548
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user sureshthalamati commented on the pull request:
https://github.com/apache/spark/pull/8676#issuecomment-139611398
next() will return false because resultset will be empty when query is
where 1!=0. executeQuery() will throw an exception if table is not found.
next() call
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8719#issuecomment-139611438
[Test build #42339 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42339/console)
for PR 8719 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8719#issuecomment-139611547
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/8720#issuecomment-139612274
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/8707#issuecomment-139612356
Over at https://issues.apache.org/jira/browse/SPARK-10544, someone
commented to mention that other types of built-in types do not seem to be
pickleable in 1.5. For
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/8707#issuecomment-139612469
Do you have any intuition for why this worked prior to 1.5 without the
changes implemented here?
---
If your project is set up for it, you can reply to this email
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/8604#issuecomment-139615564
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 this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8721#issuecomment-139622970
[Test build #42344 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42344/consoleFull)
for PR 8721 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7732#issuecomment-139585429
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/6356#issuecomment-139591295
ok to test
On Sep 11, 2015 9:25 AM, wrote:
> Okay to test
> On Sep 11, 2015 9:25 AM, "Edoardo Vacchi"
> wrote:
>
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/6356#issuecomment-139591167
Okay to test
On Sep 11, 2015 9:25 AM, "Edoardo Vacchi" wrote:
> Rerun tests?
>
> â
> Reply to this email directly
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8705
---
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 yhuai commented on the pull request:
https://github.com/apache/spark/pull/8687#issuecomment-139600569
Let's also update the title to reflect the change.
---
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 shivaram commented on the pull request:
https://github.com/apache/spark/pull/8696#issuecomment-139605764
@teramonagi Could you clarify what these profiles are meant to be ? Are
they IAM profiles or something else ?
cc @nchammas
---
If your project is set up for
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8604#issuecomment-139616577
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/8604#issuecomment-139594266
OK. I will merge #8705. Looks like this test is pretty flaky.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8246#issuecomment-139603660
[Test build #1743 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1743/consoleFull)
for PR 8246 at commit
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/8512#discussion_r39293115
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkS3Util.scala ---
@@ -0,0 +1,299 @@
+/*
+ * Licensed to the Apache Software Foundation
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/8679#issuecomment-139603485
Thanks for checking! : )
---
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 saucam commented on the pull request:
https://github.com/apache/spark/pull/8604#issuecomment-139615421
This time it fails jsonHadoopFSRelationSuite !
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8719#issuecomment-139583822
That seems reasonable. 2.10 doesn't need similar treatment? (I haven't paid
attention to the difference in a while; it may not.)
---
If your project is set up for it,
Github user saucam commented on the pull request:
https://github.com/apache/spark/pull/8604#issuecomment-139589217
phew! ohk :)
---
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/8701#issuecomment-139601645
merging
---
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 sureshthalamati commented on the pull request:
https://github.com/apache/spark/pull/8676#issuecomment-139611781
Typo in my previous comment, I meant when query is where 1=0.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
GitHub user nasokan opened a pull request:
https://github.com/apache/spark/pull/8720
[SPARK-10554][Core] Fix NPE with ShutdownHook
https://issues.apache.org/jira/browse/SPARK-10554
Fixes NPE when ShutdownHook tries to cleanup temporary folders
You can merge this pull
GitHub user andrewor14 opened a pull request:
https://github.com/apache/spark/pull/8721
[SPARK-10548] [SQL] Fix concurrent SQL executions / branch-1.5
*Note: this is for branch-1.5 only*
This is the same as #8710, but without the fix for SPARK-10563, which I
consider risky
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/8604#issuecomment-139588796
@saucam This is not your fault :) This test case uses a random SQL data
generator to test all supported data types. Seems that something goes wrong
there. However,
Github user evacchi commented on the pull request:
https://github.com/apache/spark/pull/6356#issuecomment-139590891
Rerun tests?
---
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 jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/8528#discussion_r39293299
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/param/shared/SharedParamsCodeGen.scala
---
@@ -56,7 +56,8 @@ private[shared] object SharedParamsCodeGen
Github user smartkiwi commented on the pull request:
https://github.com/apache/spark/pull/8700#issuecomment-139605916
@mengxr, @davies thanks for a hints
I'm rather new with Scala, and very interested into learning it further.
I've found the code with Python wrapper used
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/7150
---
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 andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/8710#discussion_r39296051
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -348,10 +348,27 @@ class SparkContext(config: SparkConf) extends Logging
with
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8604#issuecomment-139614826
[Test build #42341 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42341/console)
for PR 8604 at commit
Github user sethah commented on a diff in the pull request:
https://github.com/apache/spark/pull/8675#discussion_r39298668
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/classification/DecisionTreeClassifier.scala
---
@@ -166,6 +167,7 @@ private[ml] object
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8710#issuecomment-139614917
[Test build #42342 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42342/consoleFull)
for PR 8710 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8604#issuecomment-139614908
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/8721#issuecomment-139621501
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/8604#issuecomment-139588833
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8701#issuecomment-139588769
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/8701#issuecomment-139588771
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/8604#issuecomment-139593499
@liancheng I think there is something wrong with ORC. In
https://github.com/apache/spark/pull/8702, I make this test run 100 times and
seems ORC's suite failed several
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/8700#discussion_r39292344
--- Diff: python/pyspark/mllib/recommendation.py ---
@@ -156,6 +162,18 @@ def recommendProducts(self, user, num):
"""
return
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/8700#discussion_r39292338
--- Diff: python/pyspark/mllib/recommendation.py ---
@@ -85,6 +85,12 @@ class MatrixFactorizationModel(JavaModelWrapper,
JavaSaveable, JavaLoader):
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/8246#issuecomment-139603364
Did you have to rebase b/c of merge conflicts?
---
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 jkbradley commented on the pull request:
https://github.com/apache/spark/pull/8246#issuecomment-139603240
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/8715#issuecomment-139604369
It would be great to do some performance benchmarks too.
---
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/8246#issuecomment-139610433
[Test build #1743 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1743/console)
for PR 8246 at commit
Github user tgravescs closed the pull request at:
https://github.com/apache/spark/pull/8701
---
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 tgravescs commented on the pull request:
https://github.com/apache/spark/pull/8701#issuecomment-139610432
thanks @vanzin, closing
---
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 jkbradley commented on the pull request:
https://github.com/apache/spark/pull/8643#issuecomment-139610362
@yu-iskw Rather than using Java Any types and the old serialization
patterns, would it be easier to convert to a local DataFrame? We should be
able to take advantage
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/8604#issuecomment-139615840
I have already ignored that test. You will not see the noise any more.
---
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/7786#issuecomment-139586478
[Test build #42340 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42340/consoleFull)
for PR 7786 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8701#issuecomment-139588458
[Test build #42337 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42337/console)
for PR 8701 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/8707#issuecomment-139618711
Actually, one point of confusion: it looks like
`python/pyspark/serializers.py` had some methods for serializing namedtuple
classes with its `_restore` and
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/8721#issuecomment-139621671
@zsxwing please look at this one too
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8721#issuecomment-139621569
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8722#issuecomment-139623634
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 kevincox opened a pull request:
https://github.com/apache/spark/pull/8722
Update py4j to 0.9.
Py4J 0.9 has a performance improvement for `unescape_new_line` which
significantly reduces the time required to transfer large strings.
cc @angelini
You can merge
GitHub user jerryshao opened a pull request:
https://github.com/apache/spark/pull/8714
[SPARK-10588][Core] Fix wrong executor state in Master
`ExecutorAdded` can only be sent to `AppClient` when worker report back the
executor state as `LOADING`, otherwise because of concurrency
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8508#issuecomment-139480202
[Test build #42319 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42319/consoleFull)
for PR 8508 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8508#issuecomment-139480027
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8639#issuecomment-139483660
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8688#issuecomment-139487907
[Test build #42314 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42314/console)
for PR 8688 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8688#issuecomment-139488041
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 liancheng commented on the pull request:
https://github.com/apache/spark/pull/8612#issuecomment-139494192
@viirya Thanks anyway. Just would like to add that it's not a typo, but an
unfortunate Git auto-merge conflict between #8584 and #8155.
---
If your project is set up
Github user saucam commented on the pull request:
https://github.com/apache/spark/pull/8604#issuecomment-139500144
added 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 this feature
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8706#issuecomment-139503962
[Test build #42328 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42328/consoleFull)
for PR 8706 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8552#issuecomment-139505658
[Test build #42322 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42322/console)
for PR 8552 at commit
Github user WangTaoTheTonic commented on the pull request:
https://github.com/apache/spark/pull/7118#issuecomment-139505601
@navis Thanks you for the fix. I have tested "use $database" on local
Thrift Server and the function is ok.
There might still have a test failed need
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8703#issuecomment-139506829
Can you just use one `require` statement to make this more compact? and
string interpolation
---
If your project is set up for it, you can reply to this email and have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8714#issuecomment-139474584
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8714#issuecomment-139475969
[Test build #42316 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42316/consoleFull)
for PR 8714 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8457#issuecomment-139476431
[Test build #42317 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42317/consoleFull)
for PR 8457 at commit
1 - 100 of 550 matches
Mail list logo