Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8308#issuecomment-134172432
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/8308#issuecomment-134172233
**[Test build #41450 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41450/console)**
for PR 8308 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8308#issuecomment-134172434
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/8340#issuecomment-134209939
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/8340#issuecomment-134210007
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 sun-rui commented on the pull request:
https://github.com/apache/spark/pull/8276#issuecomment-134217045
rebased 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 have this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8276#issuecomment-134217584
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/8276#issuecomment-134217519
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/8373#issuecomment-134167836
Ah I see. So the release plugin isn't going to know about the updated
output path to the shade plugin? then I completely agree it has to change as it
won't work
Github user zsxwing closed the pull request at:
https://github.com/apache/spark/pull/8357
---
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 zsxwing commented on the pull request:
https://github.com/apache/spark/pull/8357#issuecomment-134175335
Closed this one because this is not a correct fix. Although
`scala.util.parsing.combinator.Parsers` is thread safe, `SqlParser` has some
`val` `Parser`s which are not
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8340#issuecomment-134213650
[Test build #41452 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41452/consoleFull)
for PR 8340 at commit
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/8308#discussion_r37745530
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -769,7 +790,9 @@ class DAGScheduler(
}
}
- /**
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8395#issuecomment-134227420
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/8033#issuecomment-134226804
[Test build #1684 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1684/consoleFull)
for PR 8033 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8340#issuecomment-134231386
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user MechCoder commented on the pull request:
https://github.com/apache/spark/pull/8304#issuecomment-134236820
ping @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 kevincox opened a pull request:
https://github.com/apache/spark/pull/8396
Fix datetime parsing in SparkSQL.
This fixes https://issues.apache.org/jira/browse/SPARK-9794 by using a real
ISO8601 parser. (courtesy of the xml component of the standard java library)
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8395#issuecomment-134242152
[Test build #1685 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1685/consoleFull)
for PR 8395 at commit
Github user kevincox commented on a diff in the pull request:
https://github.com/apache/spark/pull/8396#discussion_r37762298
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/util/DateTimeUtils.scala
---
@@ -107,30 +107,21 @@ object DateTimeUtils {
}
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8307#issuecomment-134225168
I'd like to commit this one for 1.6, at least. I think it's worth moving
into the apparent right place for 1.5 too to avoid merge conflicts and make
sure the test is
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/8396#discussion_r37761954
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/util/DateTimeUtils.scala
---
@@ -107,30 +107,21 @@ object DateTimeUtils {
}
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8396#issuecomment-134241948
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/7884#issuecomment-134246567
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/8276#issuecomment-134219790
[Test build #41453 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41453/consoleFull)
for PR 8276 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8363#issuecomment-134226021
[Test build #1683 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1683/consoleFull)
for PR 8363 at commit
GitHub user SlavikBaranov opened a pull request:
https://github.com/apache/spark/pull/8395
[SPARK-10182] [MLlib] GeneralizedLinearModel doesn't unpersist cached data
`GeneralizedLinearModel` creates a cached RDD when building a model. It's
inconvenient, since these RDDs flood the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8340#issuecomment-134231385
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/8340#issuecomment-134231152
[Test build #41452 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41452/console)
for PR 8340 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8395#issuecomment-134241071
I get it, it's maybe because the one path is not cached. This looks good to
me. The only thing I wonder is this: clearly the code is expecting that the
input should be
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8396#issuecomment-134241529
See https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark
for how to name pull requests, which would automatically link them.
---
If your project is
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7884#issuecomment-134248368
[Test build #41454 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41454/consoleFull)
for PR 7884 at commit
Github user dbtsai commented on the pull request:
https://github.com/apache/spark/pull/7884#issuecomment-134246783
Hello @jkbradley @mengxr, this is ready to be reviewed. Do you have a
chance to have a pass on this PR? Thanks.
---
If your project is set up for it, you can reply to
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7884#issuecomment-134246625
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 a diff in the pull request:
https://github.com/apache/spark/pull/8368#discussion_r37755900
--- Diff:
sql/hive-thriftserver/src/test/scala/org/apache/spark/sql/hive/thriftserver/HiveThriftServer2Suites.scala
---
@@ -377,6 +377,60 @@ class
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8363#issuecomment-134229748
[Test build #1683 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1683/consoleFull)
for PR 8363 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8395#issuecomment-134261044
[Test build #1685 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1685/console)
for PR 8395 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8340#issuecomment-134262144
[Test build #41455 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41455/consoleFull)
for PR 8340 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8383#issuecomment-134285080
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/8383#issuecomment-134284922
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/5516#issuecomment-134293472
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/8340#issuecomment-134293470
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/8340#issuecomment-134293467
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/8340#issuecomment-134293378
[Test build #41455 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41455/console)
for PR 8340 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5516#issuecomment-134293471
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 squito commented on the pull request:
https://github.com/apache/spark/pull/8180#issuecomment-134294669
Iâve only recently looked at making changes to the scheduler, but it
seems to me there is widespread agreement among committers that it is very
error prone. For
Github user eshilts commented on the pull request:
https://github.com/apache/spark/pull/5516#issuecomment-134263643
After getting the latest from master and rebuilding Spark, this now passes
all tests. It should be ready to be re-tested on Jenkins and merged.
---
If your project is
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5516#issuecomment-134270284
[Test build #41456 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41456/consoleFull)
for PR 5516 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8340#issuecomment-134258513
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/8340#issuecomment-134258417
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/5516#issuecomment-134264322
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/5516#issuecomment-134264230
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/8383#issuecomment-134290415
[Test build #41457 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41457/consoleFull)
for PR 8383 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5516#issuecomment-134293244
[Test build #41456 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41456/console)
for PR 5516 at commit
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/8373#issuecomment-134296970
LGTM. Yeah, I've been bitten by this before - the maven install plugin does
not understand `outputFile`.
---
If your project is set up for it, you can reply to this
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/8307#issuecomment-134297549
LGTM, but it would be nice to hear from the original author what was the
intent here. @chenghao-intel?
---
If your project is set up for it, you can reply to this email
GitHub user ihainan opened a pull request:
https://github.com/apache/spark/pull/8397
[SPARK-10184][Core]Optimization for bounds determination in RangePartitioner
JIRA Issue: https://issues.apache.org/jira/browse/SPARK-10184
Change `cumWeight target` to `cumWeight = target`
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8394#issuecomment-134298946
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/8397#issuecomment-134299756
That seems right. @mengxr ?
---
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/8397#issuecomment-134299684
[Test build #1686 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1686/consoleFull)
for PR 8397 at commit
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/7052#issuecomment-134303359
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/8218#issuecomment-134303181
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/8276#issuecomment-134304021
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/7629#issuecomment-134306201
[Test build #41461 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41461/consoleFull)
for PR 7629 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8276#issuecomment-134306551
[Test build #41462 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41462/consoleFull)
for PR 8276 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8394#issuecomment-134306562
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/8394#issuecomment-134306385
[Test build #41458 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41458/console)
for PR 8394 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8033#issuecomment-134307660
**[Test build #1684 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1684/console)**
for PR 8033 at commit
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/8394#issuecomment-134297751
cc @sun-rui @falaki
---
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 mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/8369#discussion_r37773632
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/tree/configuration/Strategy.scala
---
@@ -158,6 +158,11 @@ class Strategy (
s Valid values
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/8369#discussion_r37773624
--- Diff: docs/ml-decision-tree.md ---
@@ -416,61 +413,49 @@ DataFrame testData = splits[1];
// Train a DecisionTree model.
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8369#issuecomment-134298575
LGTM except some minor 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8394#issuecomment-134300092
[Test build #41458 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41458/consoleFull)
for PR 8394 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8276#issuecomment-134304025
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/8276#issuecomment-134305683
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/8276#issuecomment-134305778
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/8394#issuecomment-134306560
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/7052#issuecomment-134306478
[Test build #41459 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41459/consoleFull)
for PR 7052 at commit
Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/5636#discussion_r37780181
--- Diff:
core/src/test/scala/org/apache/spark/scheduler/DAGSchedulerSuite.scala ---
@@ -473,6 +473,280 @@ class DAGSchedulerSuite
Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/5636#discussion_r37780211
--- Diff:
core/src/test/scala/org/apache/spark/scheduler/DAGSchedulerSuite.scala ---
@@ -473,6 +473,280 @@ class DAGSchedulerSuite
Github user feynmanliang commented on the pull request:
https://github.com/apache/spark/pull/8233#issuecomment-134317463
Any reason for using a `var` instead of `val` to store the broadcast
variable?
---
If your project is set up for it, you can reply to this email and have your
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/8386#issuecomment-134297645
Thanks @yu-iskw for this change and also for sending the PDF. One question
I have is if there is any way we can change the documentation from appearing as
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/8394#issuecomment-134297737
Jenkins, 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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8397#issuecomment-134298935
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/8394#issuecomment-134298972
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/8276#issuecomment-134303924
**[Test build #41453 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41453/console)**
for PR 8276 at commit
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134303307
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/8218#issuecomment-134304652
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/7052#issuecomment-134304659
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/8218#issuecomment-134304695
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/7629#issuecomment-134304656
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/7629#issuecomment-134304697
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/7052#issuecomment-134304696
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/8276#issuecomment-134305750
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/8218#issuecomment-134306161
[Test build #41460 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41460/consoleFull)
for PR 8218 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8033#issuecomment-134308205
[Test build #1687 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1687/consoleFull)
for PR 8033 at commit
Github user feynmanliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/8166#discussion_r37781117
--- Diff: python/pyspark/mllib/linalg/__init__.py ---
@@ -841,6 +930,41 @@ def parse(s):
def zeros(size):
return
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5423#issuecomment-134324167
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/7884#issuecomment-134324919
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/7884#issuecomment-134324809
**[Test build #41454 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41454/console)**
for PR 7884 at commit
1 - 100 of 762 matches
Mail list logo
