Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1118#issuecomment-46526256
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/1118#issuecomment-46526259
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 rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1118#discussion_r13954580
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveStrategies.scala ---
@@ -17,7 +17,7 @@
package org.apache.spark.sql.hive
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1118#issuecomment-46526501
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 rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1118#discussion_r13954638
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/logical/commands.scala
---
@@ -60,3 +60,16 @@ case class ExplainCommand(plan:
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1118#discussion_r13954626
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/execution/HiveQuerySuite.scala
---
@@ -257,6 +250,88 @@ class HiveQuerySuite extends
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1118#discussion_r13954661
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveStrategies.scala ---
@@ -81,6 +81,20 @@ private[hive] trait HiveStrategies {
def
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1118#issuecomment-46526557
Merged build finished.
---
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 rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1118#discussion_r13954704
--- Diff: sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveQl.scala ---
@@ -362,13 +367,19 @@ private[hive] object HiveQl {
}
}
+
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/917#issuecomment-46526650
(Looks like this needs a rebase?)
---
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 rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1118#discussion_r13954716
--- Diff: sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveQl.scala ---
@@ -362,13 +367,19 @@ private[hive] object HiveQl {
}
}
+
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1118#issuecomment-46526720
Merged build finished.
---
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/1118#issuecomment-46526493
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/1118#issuecomment-46526721
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15897/
---
If your project is set up for it, you can
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/1124#issuecomment-46527308
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 have
Github user ash211 commented on the pull request:
https://github.com/apache/spark/pull/1019#issuecomment-46527409
I found this JETTY bug which is a potential improvement they could make.
https://jira.codehaus.org/browse/JETTY-1229
Updates to this PR forthcoming
---
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1124#issuecomment-46527415
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/1124#issuecomment-46527422
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 dongwang218 commented on the pull request:
https://github.com/apache/spark/pull/643#issuecomment-46527471
@mengxr, per your comments on stochastic update performance:
1. Training data are reordered. The effect on runtime is quite small.
2. Regularize weights after
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1105#issuecomment-46527438
Thanks, merged into 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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/1105
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/643#issuecomment-46527671
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/643#issuecomment-46527679
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 have
Github user ash211 commented on the pull request:
https://github.com/apache/spark/pull/1019#issuecomment-46527678
Latest iteration:
14/06/19 02:28:27 WARN JettyUtils: Failed to create UI on port :4040.
Trying again on port :4041 - Failure(java.net.BindException: Address
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/1019#discussion_r13955026
--- Diff: conf/log4j.properties.template ---
@@ -6,6 +6,6 @@ log4j.appender.console.layout=org.apache.log4j.PatternLayout
Github user ash211 commented on a diff in the pull request:
https://github.com/apache/spark/pull/1019#discussion_r13955085
--- Diff: conf/log4j.properties.template ---
@@ -6,6 +6,6 @@ log4j.appender.console.layout=org.apache.log4j.PatternLayout
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1019#issuecomment-46527949
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/1124#issuecomment-46527961
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15899/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1019#issuecomment-46527953
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/1124#issuecomment-46527960
Merged build finished.
---
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 kayousterhout commented on a diff in the pull request:
https://github.com/apache/spark/pull/1124#discussion_r13955115
--- Diff: core/src/main/scala/org/apache/spark/executor/Executor.scala ---
@@ -212,7 +208,12 @@ private[spark] class Executor(
val
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/643#issuecomment-46528240
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15900/
---
If your project is set up for it, you can
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/1124#issuecomment-46528231
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/643#issuecomment-46528239
Merged build finished.
---
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 a diff in the pull request:
https://github.com/apache/spark/pull/1124#discussion_r13955220
--- Diff: core/src/main/scala/org/apache/spark/executor/Executor.scala ---
@@ -212,7 +208,12 @@ private[spark] class Executor(
val
Github user ash211 commented on a diff in the pull request:
https://github.com/apache/spark/pull/1107#discussion_r13955228
--- Diff: core/src/main/scala/org/apache/spark/HttpServer.scala ---
@@ -41,45 +41,73 @@ private[spark] class ServerStateException(message:
String) extends
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1118#issuecomment-46528512
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/1124#issuecomment-46528511
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/1124#issuecomment-46528519
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/1118#issuecomment-46528520
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 mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/1124#discussion_r13955317
--- Diff: core/src/main/scala/org/apache/spark/executor/Executor.scala ---
@@ -212,7 +208,12 @@ private[spark] class Executor(
val
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/1118#discussion_r13955335
--- Diff: sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveQl.scala ---
@@ -120,6 +119,12 @@ private[hive] object HiveQl {
TOK_SWITCHDATABASE
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/940#issuecomment-46529144
@nevillelyh Is there a JIRA for it? Is it fixed in 0.8.1?
---
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 mateiz commented on the pull request:
https://github.com/apache/spark/pull/999#issuecomment-46529253
Ah yeah, this might not have been super clear, but this has at least been
my assumption. We do want to make both SQL and GraphX be non-alpha soon though,
perhaps as early
Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/1064#discussion_r13955604
--- Diff:
core/src/main/scala/org/apache/spark/shuffle/hash/HashShuffleReader.scala ---
@@ -31,10 +31,24 @@ class HashShuffleReader[K, C](
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/1064#issuecomment-46529414
Hey, sorry, been a bit busy lately but I will take a look soon. At a quick
glance it looks pretty good.
---
If your project is set up for it, you can reply to this email
Github user kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/1124#issuecomment-46529444
So this can make performance worse for folks that set spark.akka.frameSize
in the SparkConf that's on the executor to be higher, right, because this
commit means
GitHub user marmbrus opened a pull request:
https://github.com/apache/spark/pull/1129
[SPARK-2191][SQL] Make sure InsertIntoHiveTable doesn't execute more than
once.
You can merge this pull request into a Git repository by running:
$ git pull
Github user kayousterhout commented on a diff in the pull request:
https://github.com/apache/spark/pull/1124#discussion_r13955665
--- Diff: core/src/main/scala/org/apache/spark/executor/Executor.scala ---
@@ -212,7 +208,12 @@ private[spark] class Executor(
val
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1129#issuecomment-46529650
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/1129#issuecomment-46529656
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 pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/1019#discussion_r13955854
--- Diff: core/src/main/scala/org/apache/spark/ui/JettyUtils.scala ---
@@ -194,11 +194,16 @@ private[spark] object JettyUtils extends Logging {
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/1019#discussion_r13955863
--- Diff: core/src/main/scala/org/apache/spark/ui/JettyUtils.scala ---
@@ -194,11 +194,16 @@ private[spark] object JettyUtils extends Logging {
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/1124#issuecomment-46530221
For the first scenario, it won't make the performance worse because the
system doesn't really work now for serialized task result of size between 10M
and
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1019#issuecomment-46530285
Two minor things. I can just fix them on merging this if it otherwise
passes tests (of course, unless you strongly prefer saying `port :4040` instead
of `port 4040`.
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1124#issuecomment-46530379
@mengxr I think the scenario is where people have set SPARK_JAVA_OPTS in
`spark-env` and copied this to all of the nodes. In that case, the
configuration will be
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1019#issuecomment-46530538
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15901/
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1019#issuecomment-46530536
Merged build finished. All automated tests passed.
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/1124#issuecomment-46530520
@mengxr this actually hung up while running tests:
```
[info] MapOutputTrackerSuite:
[info] - compressSize
[info] - decompressSize
[info] -
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1124#issuecomment-46530537
Merged build finished.
---
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/1124#issuecomment-46530539
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15896/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1124#issuecomment-46531010
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15902/
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1124#issuecomment-46531008
Merged build finished. All automated tests passed.
---
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/1124#issuecomment-46531328
I don't get it. As long as the actor systems are created from
AkkaUtils.createActorSystem, the minimum value of the max frame size is 10M.
All unit tests passed on
Github user kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/1124#issuecomment-46531448
I see -- you're right about the min frame size. @pwendell was talking
about the first case, where I think the config parameter is currently being
correctly
GitHub user marmbrus opened a pull request:
https://github.com/apache/spark/pull/1130
[SQL] Improve Speed of InsertIntoHiveTable
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/marmbrus/spark noFunctional
Alternatively you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1130#issuecomment-46531657
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/1130#issuecomment-46531666
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/1124#issuecomment-46531776
Just tested `- 1024` in `SchedulerBackend`. The system did hang up when the
task size is close to 10M - 1024 ...
~~~
scala val random = new
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/791#issuecomment-46532970
did a manual merge :)
---
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/1118#issuecomment-46533263
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15903/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1118#issuecomment-46533262
Merged build finished.
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/1118#issuecomment-46534190
hmmm a lot of tests are failing because the output doesn't match exactly
Hive's ...
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1129#issuecomment-46534738
Merged build finished. All automated tests passed.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1129#issuecomment-46534739
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15904/
---
If your
GitHub user li-zhihui opened a pull request:
https://github.com/apache/spark/pull/1131
[SPARK-2193] Improve tasks preferrd locality by sorting tasks partial or...
Now, the last executor(s) maybe not get itâs preferred task(s), although
these tasks have build in
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1131#issuecomment-46535871
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 WangTaoTheTonic commented on the pull request:
https://github.com/apache/spark/pull/1106#issuecomment-46536007
Make it short, the commit will better balance the load strategy when there
comes a lot of drivers, while not result in bad performance when drivers is
few as
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1130#issuecomment-46536988
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15905/
---
If your
Github user mridulm commented on the pull request:
https://github.com/apache/spark/pull/1131#issuecomment-46537074
A preferred task for one worker might be picked up by another worker on
process/node/rack only if they are at the same locality level : in which case,
it is irrelevant
Github user xiajunluan commented on the pull request:
https://github.com/apache/spark/pull/1113#issuecomment-46537162
you could open a JIRA issue to describe you request.
---
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 li-zhihui commented on the pull request:
https://github.com/apache/spark/pull/1131#issuecomment-46540777
@mridulm
for example:
2 tasks(task_x, task_y), 2 executors(host1, host2)
task_x.preferredLocations = [host2, host3, host1]
task_y.preferredLocations =
GitHub user mengxr opened a pull request:
https://github.com/apache/spark/pull/1132
[SPARK-1112, 2156] Bootstrap to fetch the driver's Spark properties.
This is an alternative solution to #1124 . Before launching the executor
backend, we first fetch driver's spark properties and
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/1124#issuecomment-46541699
@pwendell @kayousterhout I put an alternative solution in #1132 . Please
let me know which do you prefer.
---
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/1132#issuecomment-46541712
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/1132#issuecomment-46541722
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/1132#issuecomment-46542119
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/1132#issuecomment-46542137
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 ueshin opened a pull request:
https://github.com/apache/spark/pull/1133
[SPARK-2196] [SQL] Fix nullability of CaseWhen.
`CaseWhen` should use `branches.length` to check if `elseValue` is provided
or not.
You can merge this pull request into a Git repository by running:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1133#issuecomment-46542932
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/1133#issuecomment-46542944
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/1132#issuecomment-46544485
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15906/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1132#issuecomment-46544481
Merged build finished.
---
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/1132#issuecomment-46544918
Merged build finished.
---
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/1132#issuecomment-46544919
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15907/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1132#issuecomment-46547412
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/1132#issuecomment-46547422
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/1133#issuecomment-46548672
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15908/
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1133#issuecomment-46548671
Merged build finished. All automated tests passed.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1132#issuecomment-46550260
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15909/
---
If your
1 - 100 of 325 matches
Mail list logo
