Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5915#issuecomment-108186295
**[Test build #877 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/877/consoleFull)**
for PR 5915 at commit
[`49b507b`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6604#issuecomment-108186506
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6604#issuecomment-108186521
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6604#issuecomment-108186575
[Test build #34061 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34061/consoleFull)
for PR 6604 at commit
[`5dccc20`](https://gith
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/6602#issuecomment-108187243
streaming flaky test. 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 yo
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6602#issuecomment-108187309
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6602#issuecomment-108187328
[Test build #34062 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34062/consoleFull)
for PR 6602 at commit
[`a75ff8f`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6602#issuecomment-108187297
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 h
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6587#issuecomment-108187502
[Test build #34056 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34056/consoleFull)
for PR 6587 at commit
[`5245542`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6587#issuecomment-108187510
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 project
GitHub user sun-rui opened a pull request:
https://github.com/apache/spark/pull/6605
[SPARK-8063][SPARKR] Spark master URL conflict between MASTER env variable
and --master command line option.
You can merge this pull request into a Git repository by running:
$ git pull https
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6605#issuecomment-108188919
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/6605#issuecomment-108188911
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 h
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/5880#issuecomment-108189021
In Spark 1.2, the SessionState should be initialized in HiveContext (or
probably in SparkSQLCLIDriver if you are using the CLI). Can you describe how
to reproduce
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6605#issuecomment-108189107
[Test build #34063 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34063/consoleFull)
for PR 6605 at commit
[`51ca48b`](https://gith
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/6328#issuecomment-108189943
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6603#issuecomment-108190611
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 project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6328#issuecomment-108190458
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6328#issuecomment-108190510
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/6601#issuecomment-108190509
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6603#issuecomment-108190578
[Test build #34053 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34053/consoleFull)
for PR 6603 at commit
[`994b3ba`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6601#issuecomment-108190440
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 h
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6328#issuecomment-108190906
[Test build #34065 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34065/consoleFull)
for PR 6328 at commit
[`3bec7b9`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6601#issuecomment-108191853
[Test build #34064 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34064/consoleFull)
for PR 6601 at commit
[`baa8ad5`](https://gith
Github user potix2 commented on the pull request:
https://github.com/apache/spark/pull/4269#issuecomment-108194195
Thank you, @JoshRosen. I got it. There is no problem to rewrite in Python.
---
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/6525#issuecomment-108194828
[Test build #34055 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34055/consoleFull)
for PR 6525 at commit
[`763b821`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6525#issuecomment-108194852
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 project
Github user nitin2goyal commented on the pull request:
https://github.com/apache/spark/pull/5880#issuecomment-108195540
Yes, I am using HiveContext and calling hiveContext.sql, basically
following line gets executed :-
https://github.com/apache/spark/blob/branch-1.2/sql/hive/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6597#issuecomment-108195638
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6597#issuecomment-108195628
[Test build #34060 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34060/consoleFull)
for PR 6597 at commit
[`c88533b`](https://git
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6222
---
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 enab
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6328#issuecomment-108196988
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6328#issuecomment-108196982
[Test build #34065 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34065/consoleFull)
for PR 6328 at commit
[`3bec7b9`](https://git
Github user harishreedharan commented on a diff in the pull request:
https://github.com/apache/spark/pull/6508#discussion_r31594720
--- Diff:
core/src/main/scala/org/apache/spark/ExecutorAllocationManager.scala ---
@@ -443,9 +466,27 @@ private[spark] class ExecutorAllocationManager
Github user eggsby commented on the pull request:
https://github.com/apache/spark/pull/6597#issuecomment-108197637
Looks like I blindly replaced some other package local references to
`parquet.ClassName` to `org.apache.parquet.ClassName` - this was really
confusing, but should be fixe
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6494#issuecomment-108197737
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6494#issuecomment-108197749
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/6597#issuecomment-108197801
Jenkins, ok to test.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feat
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5792#issuecomment-108197865
[Test build #34057 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34057/consoleFull)
for PR 5792 at commit
[`b422a08`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5792#issuecomment-108197872
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6494#issuecomment-108197910
[Test build #34066 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34066/consoleFull)
for PR 6494 at commit
[`70841e1`](https://gith
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/6605#issuecomment-108197994
hmm -- so just to confirm, does the `MASTER` env variable get read by
`spark-submit` automatically ?
---
If your project is set up for it, you can reply to this email
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6494#issuecomment-108198044
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6494#issuecomment-108198043
[Test build #34066 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34066/consoleFull)
for PR 6494 at commit
[`70841e1`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6597#issuecomment-108198121
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6597#issuecomment-108198135
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6598#issuecomment-108198318
**[Test build #34054 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34054/consoleFull)**
for PR 6598 at commit
[`e217b78`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6597#issuecomment-108198307
[Test build #34067 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34067/consoleFull)
for PR 6597 at commit
[`2df0d1b`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6598#issuecomment-108198323
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 project
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/6601#issuecomment-108200211
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5792#issuecomment-108200208
[Test build #34058 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34058/consoleFull)
for PR 5792 at commit
[`a131be6`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5792#issuecomment-108200212
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 project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6602#issuecomment-108202409
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 project
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/5880#issuecomment-108202376
Hmm, seems a bug in Spark 1.2, will cause some performance overhead
(creating the HiveConf object everytime), but, we should always initialize the
`SessionState`
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6602#issuecomment-108202403
[Test build #34062 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34062/consoleFull)
for PR 6602 at commit
[`a75ff8f`](https://git
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/5290#issuecomment-108202625
@cloud-fan do you mind reviewing 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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/6596#issuecomment-108202717
LGTM. I'm going to merge this into branch-1.4 as well. Because having param
variable name different from param.name would cause issues with Python.
---
If your project i
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6596
---
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 enab
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/6603#issuecomment-108202939
Sure, sounds good.
---
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 fe
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/6479#discussion_r31595759
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/codegen/GenerateProjection.scala
---
@@ -38,201 +42,191 @@ object GenerateProj
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6603
---
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 enab
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6328#issuecomment-108203216
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6328#issuecomment-108203224
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6328#issuecomment-108203353
[Test build #34068 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34068/consoleFull)
for PR 6328 at commit
[`2f42d02`](https://gith
Github user nitin2goyal commented on the pull request:
https://github.com/apache/spark/pull/5880#issuecomment-108204029
Yes, seems like it is being done in 1.4
https://github.com/apache/spark/blob/branch-1.4/sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveContext.scala#L
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/6596#issuecomment-108203953
OK. It's odd to have a breaking change between 1.4.0 and 1.4.1 though...
---
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/6595#issuecomment-108204988
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/6595#issuecomment-108204926
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 h
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/6595#issuecomment-108204925
I checked the transformers we have. Perhaps this is the only one that would
operate on target labels, and it is blocking users from making predictions
without labels. So
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6595#issuecomment-108205564
[Test build #34069 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34069/consoleFull)
for PR 6595 at commit
[`b6a36b9`](https://gith
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/6584#discussion_r31596223
--- Diff: docs/mllib-linear-methods.md ---
@@ -282,8 +277,8 @@ public class SVMClassifier {
System.out.println("Area under ROC = " + auROC);
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6584
---
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 enab
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6494#issuecomment-108207374
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6494#issuecomment-108207416
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/6587#issuecomment-108207357
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6587#issuecomment-108207417
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6604#issuecomment-108207751
[Test build #34061 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34061/consoleFull)
for PR 6604 at commit
[`5dccc20`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6604#issuecomment-108207778
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 project
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/6584#issuecomment-108207886
LGTM. Merged into master and branch-1.4. 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 p
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6494#issuecomment-108207979
[Test build #34071 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34071/consoleFull)
for PR 6494 at commit
[`4d28012`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6587#issuecomment-108207950
[Test build #34070 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34070/consoleFull)
for PR 6587 at commit
[`560da1a`](https://gith
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/6538#discussion_r31596512
--- Diff: mllib/src/main/scala/org/apache/spark/mllib/util/MLUtils.scala ---
@@ -82,6 +82,17 @@ object MLUtils {
val value = indexAndValue(1).toD
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/6538#discussion_r31596514
--- Diff: mllib/src/main/scala/org/apache/spark/mllib/util/MLUtils.scala ---
@@ -82,6 +82,17 @@ object MLUtils {
val value = indexAndValue(1).toD
Github user animeshbaranawal commented on the pull request:
https://github.com/apache/spark/pull/6553#issuecomment-108208499
@rxin
To include the range(end) functioning in python sql context, the only way I
could figure out is to re-order the function arguments in range which is n
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6579
---
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 enab
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/6579#issuecomment-108208918
LGTM. Merged into master and all branches since 1.0. Thanks!
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/6553#issuecomment-108208929
It is ok. You can just use start itself, i.e. if there is only one
argument, then start means end.
---
If your project is set up for it, you can reply to this email and ha
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6595#issuecomment-108209364
[Test build #34069 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34069/consoleFull)
for PR 6595 at commit
[`b6a36b9`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6595#issuecomment-108209375
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 project
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/6562#issuecomment-108209311
@jkbradley If we want to include it in 1.4.1, we can merge it into
branch-1.4 now and set the fix version to 1.4.1 and 1.5.0. If RC4 doesn't pass
the vote, @pwendell will
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6605#issuecomment-108212713
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6605#issuecomment-108212702
[Test build #34063 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34063/consoleFull)
for PR 6605 at commit
[`51ca48b`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6602#issuecomment-108213042
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6598#issuecomment-108213099
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/6598#issuecomment-108212938
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/6602#issuecomment-108212874
Weird objenesis failures again. 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6602#issuecomment-108213100
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/6598#issuecomment-108213058
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6587#issuecomment-108213528
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6602#issuecomment-108213579
[Test build #34072 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34072/consoleFull)
for PR 6602 at commit
[`a75ff8f`](https://gith
801 - 900 of 906 matches
Mail list logo
