Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/662#issuecomment-42272627
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14705/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/662#issuecomment-42272626
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/475#issuecomment-42272629
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14706/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/475#issuecomment-42272628
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 have
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/475#discussion_r12312446
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/tree/configuration/Strategy.scala
---
@@ -35,6 +35,9 @@ import
org.apache.spark.mllib.tree.configuration
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/448#issuecomment-42272515
@kanzhang this is out of date with master - mind merging it?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as wel
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/475#discussion_r12312438
--- Diff:
mllib/src/test/scala/org/apache/spark/mllib/tree/DecisionTreeSuite.scala ---
@@ -405,16 +453,30 @@ object DecisionTreeSuite {
def generat
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/475#discussion_r12312434
--- Diff:
mllib/src/test/scala/org/apache/spark/mllib/tree/DecisionTreeSuite.scala ---
@@ -390,13 +391,60 @@ class DecisionTreeSuite extends FunSuite with
Befo
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/653#discussion_r12312420
--- Diff: mllib/data/sample_naive_bayes_data.txt ---
@@ -1,6 +1,6 @@
-0, 1 0 0
-0, 2 0 0
-1, 0 1 0
-1, 0 2 0
-2, 0 0 1
-2, 0 0 2
+0,1
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/475#issuecomment-42272361
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/475#issuecomment-42272366
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 mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/653#discussion_r12312343
--- Diff: docs/configuration.md ---
@@ -26,10 +26,10 @@ application name), as well as arbitrary key-value pairs
through the `set()` meth
initialize an appl
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/662#issuecomment-42272156
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/475#issuecomment-42272159
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/475#issuecomment-42272151
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/662#issuecomment-42272149
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 ha
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/662#discussion_r12312305
--- Diff: docs/index.md ---
@@ -50,23 +51,6 @@ options for deployment:
* [Apache Mesos](running-on-mesos.html)
* [Hadoop YARN](running-on-yarn.html)
Github user manishamde commented on the pull request:
https://github.com/apache/spark/pull/475#issuecomment-42272079
@mengxr Thanks for the feedback. The review and corresponding edits
happened in real-time. :-)
---
If your project is set up for it, you can reply to this email and h
GitHub user pwendell opened a pull request:
https://github.com/apache/spark/pull/662
Fix two download suggestions in the docs:
1) On the quick start page provide a direct link to the downloads
(suggested by @pbailis).
2) On the index page, don't suggest users always have to buil
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/475#issuecomment-42271981
@manishamde Could you mention how to configure `maxMemoryInMB` in the
programming guide?
---
If your project is set up for it, you can reply to this email and have your
re
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/475#discussion_r12312185
--- Diff:
mllib/src/test/scala/org/apache/spark/mllib/tree/DecisionTreeSuite.scala ---
@@ -412,6 +460,20 @@ object DecisionTreeSuite {
arr
}
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/475#discussion_r12312167
--- Diff:
mllib/src/test/scala/org/apache/spark/mllib/tree/DecisionTreeSuite.scala ---
@@ -390,6 +391,53 @@ class DecisionTreeSuite extends FunSuite with
Befor
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/475#issuecomment-42271750
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/475#issuecomment-42271752
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/658
---
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 enabl
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/653#discussion_r12311753
--- Diff: docs/configuration.md ---
@@ -26,10 +26,10 @@ application name), as well as arbitrary key-value pairs
through the `set()` meth
initialize an appl
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/475#discussion_r12311733
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/tree/DecisionTree.scala ---
@@ -269,7 +296,50 @@ object DecisionTree extends Serializable with Logging {
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/653#discussion_r12311692
--- Diff: mllib/data/sample_naive_bayes_data.txt ---
@@ -1,6 +1,6 @@
-0, 1 0 0
-0, 2 0 0
-1, 0 1 0
-1, 0 2 0
-2, 0 0 1
-2, 0 0 2
+0,1
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/475#discussion_r12311646
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/tree/DecisionTree.scala ---
@@ -269,7 +296,50 @@ object DecisionTree extends Serializable with Logging {
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/475#discussion_r12311634
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/tree/DecisionTree.scala ---
@@ -68,7 +69,28 @@ class DecisionTree (private val strategy: Strategy)
extend
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/475#discussion_r12311590
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/tree/DecisionTree.scala ---
@@ -68,7 +69,28 @@ class DecisionTree (private val strategy: Strategy)
extend
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/475#discussion_r12311588
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/tree/DecisionTree.scala ---
@@ -68,7 +69,28 @@ class DecisionTree (private val strategy: Strategy)
extend
Github user funes commented on a diff in the pull request:
https://github.com/apache/spark/pull/661#discussion_r12311565
--- Diff: mllib/src/main/scala/org/apache/spark/mllib/linalg/Vectors.scala
---
@@ -136,7 +136,7 @@ object Vectors {
new DenseVector(v.toArray) //
Github user funes closed the pull request at:
https://github.com/apache/spark/pull/661
---
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 enable
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/658#issuecomment-42270155
Thanks, going to merge this in.
---
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 hav
Github user manishamde commented on the pull request:
https://github.com/apache/spark/pull/475#issuecomment-42270061
@mengxr Sorry for troubling you. If you have time, could you take another
look and provide feedback (if any). A few more tree-based PRs are in the
pipeline and it's bes
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/653#discussion_r12311477
--- Diff: docs/configuration.md ---
@@ -26,10 +26,10 @@ application name), as well as arbitrary key-value pairs
through the `set()` meth
initialize an appl
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/653#discussion_r12311457
--- Diff: mllib/data/sample_naive_bayes_data.txt ---
@@ -1,6 +1,6 @@
-0, 1 0 0
-0, 2 0 0
-1, 0 1 0
-1, 0 2 0
-2, 0 0 1
-2, 0 0 2
+0,1
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/661#discussion_r12311400
--- Diff: mllib/src/main/scala/org/apache/spark/mllib/linalg/Vectors.scala
---
@@ -136,7 +136,7 @@ object Vectors {
new DenseVector(v.toArray) /
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/653#discussion_r12311331
--- Diff: mllib/data/sample_naive_bayes_data.txt ---
@@ -1,6 +1,6 @@
-0, 1 0 0
-0, 2 0 0
-1, 0 1 0
-1, 0 2 0
-2, 0 0 1
-2, 0 0 2
+0,1
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/653#discussion_r12311279
--- Diff: docs/configuration.md ---
@@ -26,10 +26,10 @@ application name), as well as arbitrary key-value pairs
through the `set()` meth
initialize an appl
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/597#issuecomment-42269236
Can I make a tiny suggestion to map from ratings to weights with something
like "rating - 2.5" instead of "rating - 3"? So that 3 becomes a small positive
value like 0.5?
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/640#issuecomment-42269224
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14703/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/640#issuecomment-42269223
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 have
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/660
---
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 enabl
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/660#issuecomment-42268990
Ah, nice one, I missed out this part. This looks both correct and like a
good reorganization.
---
If your project is set up for it, you can reply to this email and have yo
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/448#issuecomment-42268877
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 an
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/448#issuecomment-42268837
LGTM then - I looked around a bit and it seems like this use case is
exactly what `this.type` is for in Scala.
@marmbrus @mateiz any further feedback?
---
If yo
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/660#issuecomment-42268616
Thanks Andrew, looks good. I'm merging 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 proje
Github user lianhuiwang commented on a diff in the pull request:
https://github.com/apache/spark/pull/636#discussion_r12310983
--- Diff: core/src/main/scala/org/apache/spark/deploy/master/Master.scala
---
@@ -523,6 +504,89 @@ private[spark] class Master(
}
}
Github user lianhuiwang commented on a diff in the pull request:
https://github.com/apache/spark/pull/636#discussion_r12310911
--- Diff: core/src/main/scala/org/apache/spark/deploy/master/Master.scala
---
@@ -523,6 +504,89 @@ private[spark] class Master(
}
}
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/660#issuecomment-42267878
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. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/640#issuecomment-42267875
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/640#issuecomment-42267876
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14700/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/640#issuecomment-42267871
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/660#issuecomment-42267879
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14701/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/640#issuecomment-42267873
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14699/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/658#issuecomment-42266840
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14697/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/658#issuecomment-42266838
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. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/659#issuecomment-42266535
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14696/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/659#issuecomment-42266534
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/640#issuecomment-42266323
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/640#issuecomment-42266320
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/661#issuecomment-42266149
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 proj
Github user kanzhang commented on the pull request:
https://github.com/apache/spark/pull/448#issuecomment-42266085
@pwendell yes, scalap shows 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 your project does not h
GitHub user funes opened a pull request:
https://github.com/apache/spark/pull/661
Bug fix of sparse vector conversion
Fixed a small bug caused by the inconsistency of index/data array size and
vector length.
You can merge this pull request into a Git repository by running:
$ g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/640#issuecomment-42265795
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14702/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/640#issuecomment-42265794
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/660#issuecomment-42265768
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/640#issuecomment-42265769
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/640#issuecomment-42265760
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/660#issuecomment-42265758
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 ha
GitHub user andrewor14 opened a pull request:
https://github.com/apache/spark/pull/660
[Spark-1735] Add the missing special profiles to make-distribution.sh
73b0cbcc241cca3d318ff74340e80b02f884acbd introduced a few special profiles
that are not covered in the `make-distribution.sh`.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/640#issuecomment-42265606
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/640#issuecomment-42265598
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/640#issuecomment-42265254
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/640#issuecomment-42265262
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/640#issuecomment-42264941
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14698/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/640#issuecomment-42264902
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/640#issuecomment-42264940
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/640#issuecomment-42264898
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 ha
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/608
---
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 enabl
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/448#issuecomment-42264854
@marmbrus anyways I don't see this tying our hands much in the future, so
seems like a good idea. It will potentially force people to re-compile coming
from pre-1.0 since
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/448#issuecomment-42264759
@marmbrus I did some local byte code inspection and I think it's injecting
this information into the scalasig of the class (in our case, the RDD class). I
made a simple c
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/658#issuecomment-42264512
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/658#issuecomment-42264503
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 featur
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/658#issuecomment-42264507
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 ha
Github user aarondav closed the pull request at:
https://github.com/apache/spark/pull/618
---
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 ena
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/448#issuecomment-42264403
I don't think it's very obvious :)
My guess would be that this.type is included in a scala specific signature
somewhere, and the scala compiler adds casts after a
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/597#issuecomment-42264123
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14695/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/597#issuecomment-42264121
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. If
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/448#issuecomment-42262939
@marmbrus @kanzhang I'm a bit confused how the bytecode could be totally
unchanged.
Let's say I create a new class `FooRDD.scala` in a totally different
package
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/658#issuecomment-42262276
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/658#issuecomment-42262278
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14694/
---
If your project is set up for it, you can r
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/608#issuecomment-42261994
Thanks - I can merge 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 not have t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/659#issuecomment-42261964
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/659#issuecomment-42261960
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 ha
GitHub user CodingCat opened a pull request:
https://github.com/apache/spark/pull/659
SPARK-1603: use auto-generated name in JobScheduler Actor
When Jenkins is pretty busy, the test of the "stop gracefully" case in
StreamingContextSuite sometimes failed with an unrelated change, the
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/652#discussion_r12309057
--- Diff:
streaming/src/test/scala/org/apache/spark/streaming/StreamingContextSuite.scala
---
@@ -183,6 +183,7 @@ class StreamingContextSuite extends FunSuite wi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/597#issuecomment-42261805
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 ha
1 - 100 of 371 matches
Mail list logo
