Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/673#issuecomment-42387240
This test was stuck so I killed it, let's try again. Jenkins retest this
please.
```
[info] - repeatedly failing task that crashes JVM (7 seconds, 56
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/690#issuecomment-42520178
We are incorrectly detecting the `Option`s as repeated types (`Seq`), which
are not supported in parquet yet.
[Fix here](https://github.com/ash211/spark/pull/1)
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/777#issuecomment-43156225
The problem is users won't be able to build these example programs unless
they are using Java 8.
---
If your project is set up for it, you can reply to this email and have
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/755#issuecomment-43131213
I see, I think that with this change, we'd promise to keep the pickle
serializer's output the same in future versions, which should be easy. We can
always add a new
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/765#issuecomment-43158373
Thanks. Merged.
---
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/683#issuecomment-42489550
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14784/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/143#issuecomment-43133585
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. If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/766#issuecomment-43159077
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/782#issuecomment-43160278
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/497#issuecomment-42480505
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/682#issuecomment-42478441
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/688
---
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/475#issuecomment-42469139
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14778/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/699#issuecomment-42591478
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 mengxr opened a pull request:
https://github.com/apache/spark/pull/775
[FIX] do not load defaults when testing SparkConf in pyspark
The default constructor loads default properties, which can fail the test.
You can merge this pull request into a Git repository by
Github user ankurdave commented on a diff in the pull request:
https://github.com/apache/spark/pull/497#discussion_r12456738
--- Diff:
graphx/src/main/scala/org/apache/spark/graphx/impl/RoutingTablePartition.scala
---
@@ -0,0 +1,158 @@
+/*
+ * Licensed to the Apache
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/597#discussion_r12388654
--- Diff:
examples/src/main/scala/org/apache/spark/examples/mllib/MovieLensALS.scala ---
@@ -88,7 +92,27 @@ object MovieLensALS {
val ratings =
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/707#issuecomment-42631585
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 ash211 commented on the pull request:
https://github.com/apache/spark/pull/695#issuecomment-42585395
Here's a little more context about that method:
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/661#discussion_r12414571
--- Diff:
mllib/src/test/scala/org/apache/spark/mllib/linalg/BreezeVectorConversionSuite.scala
---
@@ -55,4 +55,16 @@ class BreezeVectorConversionSuite
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/702#discussion_r12501401
--- Diff: docs/mllib-optimization.md ---
@@ -163,3 +171,108 @@ each iteration, to compute the gradient direction.
Available algorithms for gradient
Github user dongwang218 commented on a diff in the pull request:
https://github.com/apache/spark/pull/643#discussion_r12463354
--- Diff:
examples/src/main/scala/org/apache/spark/examples/mllib/BinaryClassification.scala
---
@@ -90,55 +135,104 @@ object BinaryClassification {
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/782#issuecomment-43162215
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/702#issuecomment-42724251
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/676#issuecomment-42393184
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/629#issuecomment-42644509
`json4s` is a direct dependency of Spark core. It's not related to the
changes here. It sounds like something is running but being pointed to an
artifact that does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/713#issuecomment-42648616
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/686#issuecomment-42494197
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/636#issuecomment-42596707
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14819/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/687#issuecomment-42513366
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/497#issuecomment-42487496
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/690#issuecomment-42517270
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/723#issuecomment-42753817
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14872/
---
If your project
Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/783#issuecomment-43163719
@marmbrus The whole point of this function was to catch and print
Throwable. It is intended to be used in places where the exception would
otherwise be silently masked,
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/761#issuecomment-43040916
Thanks. Merged!
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/708#issuecomment-42634479
LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/680#issuecomment-42409172
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/782#issuecomment-43164159
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 pjopensource commented on the pull request:
https://github.com/apache/spark/pull/693#issuecomment-42554050
yes, it's specific to spark.
2014-05-08 20:52 GMT+08:00 Sean Owen notificati...@github.com:
I don't think it's intended that you use sbt/sbt
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/709#issuecomment-42633261
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 pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/682#discussion_r12407476
--- Diff: docs/building-with-maven.md ---
@@ -129,6 +128,10 @@ Java 8 tests are run when -Pjava8-tests profile is
enabled, they will run in spi
For
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/694#issuecomment-43165266
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/702#issuecomment-42727301
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/703#issuecomment-42622268
@dbtsai Thanks! I did a grep but I forgot the docs ... LGTM.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/700#issuecomment-42610630
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/561#issuecomment-42460751
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/644#issuecomment-42754111
Okay I'll pull this in. Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/768#issuecomment-43111605
Jenkins, 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
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/754#issuecomment-43166533
Jenkins, 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/475#issuecomment-42495601
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 bouk commented on a diff in the pull request:
https://github.com/apache/spark/pull/651#discussion_r12453648
--- Diff: sbin/spark-executor ---
@@ -19,5 +19,10 @@
FWDIR=$(cd `dirname $0`/..; pwd)
+sbin=`dirname $0`
+sbin=`cd $sbin; pwd`
+
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/685#issuecomment-43141642
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/603#issuecomment-42469135
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/622#issuecomment-42700860
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 kanzhang commented on the pull request:
https://github.com/apache/spark/pull/760#issuecomment-43168454
Looked at Scaladoc just now, zip() assumes same number of elements in each
partition, so we just verify that?
---
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/784#issuecomment-43168467
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/784#issuecomment-43168472
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/711#issuecomment-42647848
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14845/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/636#issuecomment-42512928
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14802/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/685#issuecomment-43140075
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/785#issuecomment-43168881
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/784#issuecomment-43169081
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 willb commented on the pull request:
https://github.com/apache/spark/pull/143#issuecomment-42712135
I'm not able to reproduce the above failure locally (either on OS X or
Linux).
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/702#issuecomment-42724244
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/704#issuecomment-42634544
Okay cool - I'll pull that change in when I merge it.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/675#issuecomment-42504673
This should be ready for 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
Github user mridulm commented on a diff in the pull request:
https://github.com/apache/spark/pull/636#discussion_r12381063
--- Diff: core/src/main/scala/org/apache/spark/deploy/master/Master.scala
---
@@ -523,6 +504,90 @@ private[spark] class Master(
}
}
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/704#issuecomment-42635009
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14841/
---
If your project
GitHub user scwf opened a pull request:
https://github.com/apache/spark/pull/714
ãSPARK-1779ãadd warning when memoryFraction is not between 0 and 1
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/scwf/spark memoryFraction
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/675#issuecomment-42402425
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 pjopensource commented on the pull request:
https://github.com/apache/spark/pull/693#issuecomment-42527084
https://issues.apache.org/jira/browse/SPARK-1759
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/651#issuecomment-42451825
Mind creating a JIRA for this? If you could post the exception or issue
that occurs it would be helfpul.
---
If your project is set up for it, you can reply to this
Github user ankurdave commented on a diff in the pull request:
https://github.com/apache/spark/pull/497#discussion_r12456417
--- Diff:
graphx/src/main/scala/org/apache/spark/graphx/impl/RoutingTablePartition.scala
---
@@ -0,0 +1,158 @@
+/*
+ * Licensed to the Apache
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/644#issuecomment-42753677
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/644
---
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/636#issuecomment-42662663
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/675#issuecomment-42400543
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 mateiz commented on the pull request:
https://github.com/apache/spark/pull/782#issuecomment-43170117
Cool, thanks. I had some bugs in it earlier but I don't see any now.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/700#issuecomment-42611985
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/597#issuecomment-42502536
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/497#issuecomment-42491309
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 kscaldef commented on the pull request:
https://github.com/apache/spark/pull/223#issuecomment-42584832
What's the current status of this?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/717#issuecomment-42730477
@willb the re-partition issue is not related to your patch. There was an
inadvertent check-in in master that caused it. It has been fixed.
---
If your project is set up
Github user andrewor14 closed the pull request at:
https://github.com/apache/spark/pull/779
---
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/685#issuecomment-42503646
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/636#issuecomment-42593561
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14815/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/709#issuecomment-42634580
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14840/
---
If your project
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/539#issuecomment-42630957
I've merged this, thanks.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/780#issuecomment-43154166
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/685#issuecomment-43171670
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 ueshin opened a pull request:
https://github.com/apache/spark/pull/689
[SPARK-1754] [SQL] Add missing arithmetic DSL operations.
Add missing arithmetic DSL operations: `unary_-`, `%`.
You can merge this pull request into a Git repository by running:
$ git pull
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/724#issuecomment-42757145
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 pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/651#discussion_r12450389
--- Diff: sbin/spark-executor ---
@@ -19,5 +19,10 @@
FWDIR=$(cd `dirname $0`/..; pwd)
+sbin=`dirname $0`
--- End diff --
Github user mridulm commented on a diff in the pull request:
https://github.com/apache/spark/pull/636#discussion_r12380632
--- Diff: core/src/main/scala/org/apache/spark/deploy/master/Master.scala
---
@@ -523,6 +504,90 @@ private[spark] class Master(
}
}
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/636#issuecomment-42608171
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/702#issuecomment-42624702
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/694#issuecomment-43058710
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14973/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/782#issuecomment-43160050
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/636#issuecomment-42576283
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 willb reopened a pull request:
https://github.com/apache/spark/pull/143
SPARK-897: preemptively serialize closures
These commits cause `ClosureCleaner.clean` to attempt to serialize the
cleaned closure with the default closure serializer and throw a
`SparkException`
1 - 100 of 422 matches
Mail list logo
