GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/7669
[SPARK-9354][SQL] Remove Internal.get generic getter call in Hive
integration code.
I passed the data types throughout.
You can merge this pull request into a Git repository by running:
$ git
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/6986#discussion_r35490287
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/datetimeFunctions.scala
---
@@ -258,3 +258,62 @@ case class
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/6986#discussion_r35490281
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/datetimeFunctions.scala
---
@@ -258,3 +258,62 @@ case class
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7623#issuecomment-124954882
[Test build #38459 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38459/consoleFull)
for PR 7623 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7259#issuecomment-124954892
[Test build #1202 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1202/consoleFull)
for PR 7259 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7623#issuecomment-124954889
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/7623#issuecomment-124954891
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/7644#discussion_r35490360
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/datetimeFunctions.scala
---
@@ -247,14 +248,112 @@ case class
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4229#issuecomment-124957541
[Test build #38462 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38462/consoleFull)
for PR 4229 at commit
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/7669#issuecomment-124962823
A typo in PR title: Internal = InternalRow
---
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/7441#issuecomment-124963709
[Test build #38458 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38458/console)
for PR 7441 at commit
Github user yanboliang commented on the pull request:
https://github.com/apache/spark/pull/7474#issuecomment-124963664
@rxin
---
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 yanboliang opened a pull request:
https://github.com/apache/spark/pull/7672
[SPARK-9308] [ML] ml.NaiveBayesModel support predicting class probabilities
Make NaiveBayesModel support predicting class probabilities, inherit from
ProbabilisticClassificationModel.
You can
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7671#issuecomment-124966410
[Test build #38463 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38463/console)
for PR 7671 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7671#issuecomment-124966414
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/7674#issuecomment-124966397
[Test build #38467 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38467/consoleFull)
for PR 7674 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7674#issuecomment-124968686
[Test build #38469 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38469/consoleFull)
for PR 7674 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7671#issuecomment-124968674
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/7671#issuecomment-124968676
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/7671#issuecomment-124968680
[Test build #38470 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38470/consoleFull)
for PR 7671 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7671#issuecomment-124968689
[Test build #106 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SlowSparkPullRequestBuilder/106/consoleFull)
for PR 7671 at commit
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/7226#issuecomment-124972793
Should we make `IntervalType` an `AtomicType`?
---
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/7667#issuecomment-124977276
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 watermen commented on the pull request:
https://github.com/apache/spark/pull/7536#issuecomment-124995874
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 cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/7666#discussion_r35489926
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/SpecificMutableRow.scala
---
@@ -221,6 +221,10 @@ final class
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/7666#discussion_r35489834
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/InternalRow.scala ---
@@ -32,32 +32,36 @@ abstract class InternalRow extends Serializable {
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/7666#discussion_r35489827
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/InternalRow.scala ---
@@ -32,32 +32,36 @@ abstract class InternalRow extends
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7669#issuecomment-124952384
[Test build #38456 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38456/consoleFull)
for PR 7669 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7670#issuecomment-124953164
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/7670#issuecomment-124953137
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/7623#issuecomment-124956218
[Test build #38460 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38460/consoleFull)
for PR 7623 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7671#issuecomment-124957827
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7672#issuecomment-124963767
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/7441#issuecomment-124963739
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7672#issuecomment-124963765
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 Jiechor commented on the pull request:
https://github.com/apache/spark/pull/1719#issuecomment-124967482
The RDDâstorage in the algorithm default persist in memory?@mengxr
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7673#issuecomment-124969865
[Test build #38471 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38471/consoleFull)
for PR 7673 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7583#issuecomment-124969877
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 yjshen commented on the pull request:
https://github.com/apache/spark/pull/7667#issuecomment-124976717
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 cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/7673#issuecomment-124984577
cc @liancheng
---
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 x77a1 opened a pull request:
https://github.com/apache/spark/pull/7675
Merge pull request #1 from apache/master
Merge
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/x77a1/spark master
Alternatively you can review
Github user x77a1 closed the pull request at:
https://github.com/apache/spark/pull/7675
---
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/6955#issuecomment-124952308
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6955#issuecomment-124952244
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/6955#issuecomment-124952247
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/6955#issuecomment-124952241
[Test build #104 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SlowSparkPullRequestBuilder/104/consoleFull)
for PR 6955 at commit
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/7623#discussion_r35490126
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/SQLContext.scala ---
@@ -798,8 +798,13 @@ class SQLContext(@transient val sparkContext:
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/6986#discussion_r35490337
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/datetimeFunctions.scala
---
@@ -258,3 +258,62 @@ case class
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/6986#discussion_r35490339
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/datetimeFunctions.scala
---
@@ -258,3 +258,62 @@ case class
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/6986#discussion_r35490343
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/datetimeFunctions.scala
---
@@ -258,3 +258,62 @@ case class
GitHub user cloud-fan opened a pull request:
https://github.com/apache/spark/pull/7674
[SPARK-8608][SQL] DataFrame with random columns should return same value
when call show
We will do local projection for LocalRelation, and thus reuse the same
Expression object among multiply
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7673#issuecomment-124966168
[Test build #38466 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38466/console)
for PR 7673 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7673#issuecomment-124966170
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/7623#issuecomment-124967512
[Test build #38459 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38459/console)
for PR 7623 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7623#issuecomment-124967530
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 project does
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7667#issuecomment-124967558
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/7667#issuecomment-124967556
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/7674#issuecomment-124976451
[Test build #38469 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38469/console)
for PR 7674 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7674#issuecomment-124976473
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7667#issuecomment-124998683
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/7667#issuecomment-124998618
[Test build #38472 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38472/console)
for PR 7667 at commit
GitHub user GeorgeDittmar opened a pull request:
https://github.com/apache/spark/pull/7670
[Spark-7423][MLLIB] Modify ClassificationModel and Probabalistic model to
use Vector.argmax
Use Vector.argmax call instead of converting to dense vector before
calculating predictions.
You
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/7644#discussion_r35490365
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/datetimeFunctions.scala
---
@@ -247,14 +248,112 @@ case class
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/7644#discussion_r35490369
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/functions.scala ---
@@ -2419,6 +2419,44 @@ object functions {
*/
def weekofyear(columnName:
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/4229#issuecomment-124955258
@prabeesh fixed some issues in your PR here:
https://github.com/zsxwing/spark/commit/d07f45490a9554c1e3ea9c76956f383a511a2e1f
Could you take a look?
---
If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7668#issuecomment-124955615
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/7668#issuecomment-124955502
[Test build #38453 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38453/console)
for PR 7668 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7669#issuecomment-124958172
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/7669#issuecomment-124958161
[Test build #38456 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38456/console)
for PR 7669 at commit
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/7583#issuecomment-124963403
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/7583#issuecomment-124963415
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/7583#issuecomment-124963412
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 cloud-fan opened a pull request:
https://github.com/apache/spark/pull/7673
[SPARK-9355][SQL] Remove InternalRow.get generic getter call in columnar
cache code
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/7673#issuecomment-124964723
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/7673#issuecomment-124964713
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/7674#issuecomment-124967752
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/7674#issuecomment-124967748
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/7667#issuecomment-124967726
[Test build #38468 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38468/consoleFull)
for PR 7667 at commit
Github user yjshen commented on the pull request:
https://github.com/apache/spark/pull/7671#issuecomment-124967728
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/7671#issuecomment-124967750
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/7671#issuecomment-124967756
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/7673#issuecomment-124969486
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 viirya commented on the pull request:
https://github.com/apache/spark/pull/7238#issuecomment-124969522
ping @liancheng
Any other 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7673#issuecomment-124969504
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/7671#issuecomment-124976504
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7671#issuecomment-124976500
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/7671#issuecomment-124976480
[Test build #106 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SlowSparkPullRequestBuilder/106/console)
for PR 7671 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7671#issuecomment-124976483
[Test build #38470 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38470/console)
for PR 7671 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4229#issuecomment-124997223
[Test build #109 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SlowSparkPullRequestBuilder/109/consoleFull)
for PR 4229 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4229#issuecomment-124997257
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/7667#issuecomment-124997259
[Test build #107 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SlowSparkPullRequestBuilder/107/console)
for PR 7667 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4229#issuecomment-124997242
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/4229#issuecomment-124997174
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/7536#issuecomment-124997200
[Test build #38473 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38473/consoleFull)
for PR 7536 at commit
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/4229#issuecomment-124997134
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/4229#issuecomment-124997185
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/7583#issuecomment-124953350
[Test build #38454 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38454/console)
for PR 7583 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7583#issuecomment-124953354
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7623#issuecomment-124954747
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7623#issuecomment-124954754
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 this
1 - 100 of 517 matches
Mail list logo
