Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/6525#issuecomment-108177453
I will merge it once it passes tests.
---
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 eggsby commented on the pull request:
https://github.com/apache/spark/pull/6597#issuecomment-108177909
Figured it out, that was a package local reference - I actually missed some
string based classloading using the old package names.
Working on a fix now.
---
If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6538#issuecomment-108178964
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/6538#issuecomment-108178957
[Test build #34046 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34046/consoleFull)
for PR 6538 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5792#issuecomment-108179260
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 eggsby commented on the pull request:
https://github.com/apache/spark/pull/6597#issuecomment-108179149
Fixed the pyspark examples and the Class.forName classloading in the test
suites.
I've been having trouble running these integration tests on my laptop,
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5792#issuecomment-108179248
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 davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/6601#discussion_r31591860
--- Diff: python/pyspark/sql/context.py ---
@@ -196,7 +199,7 @@ def _inferSchema(self, rdd, samplingRatio=None):
can not
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5792#issuecomment-108179424
[Test build #34057 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34057/consoleFull)
for PR 5792 at commit
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/6601#discussion_r31591940
--- Diff: python/pyspark/sql/context.py ---
@@ -378,39 +378,12 @@ def parquetFile(self, *paths):
jdf = self._ssql_ctx.parquetFile(jpaths)
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/6601#discussion_r31591932
--- Diff: python/pyspark/sql/context.py ---
@@ -359,18 +365,12 @@ def registerDataFrameAsTable(self, df, tableName):
else:
raise
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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 :-
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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 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
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
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
Github user XuTingjun commented on the pull request:
https://github.com/apache/spark/pull/6545#issuecomment-107912763
@tsudukim Sorry, I don't agree with you,
spark.history.retainedApplications can't to be 0 I think
---
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/6577#issuecomment-107912862
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/6494#issuecomment-107915870
[Test build #33976 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33976/consoleFull)
for PR 6494 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6494#issuecomment-107915877
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/6538#issuecomment-107904711
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/6409#issuecomment-107904636
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/6538#issuecomment-107904738
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
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/6538#discussion_r31507411
--- Diff: mllib/src/main/scala/org/apache/spark/mllib/util/MLUtils.scala ---
@@ -82,6 +82,19 @@ object MLUtils {
val value =
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6409#issuecomment-107902722
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/6409#issuecomment-107902691
[Test build #33973 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33973/consoleFull)
for PR 6409 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6409#issuecomment-107904620
[Test build #33974 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33974/consoleFull)
for PR 6409 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6358#issuecomment-107910217
[Test build #33975 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33975/consoleFull)
for PR 6358 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6358#issuecomment-107910225
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/6538#issuecomment-107905302
[Test build #33979 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33979/consoleFull)
for PR 6538 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6547#issuecomment-107905879
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/6547#issuecomment-107905862
[Test build #33972 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33972/consoleFull)
for PR 6547 at commit
GitHub user kurochan opened a pull request:
https://github.com/apache/spark/pull/6582
[SPARK-8040] [Core] remove Debian specific loopback address setting code
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kurochan/spark
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6577#issuecomment-107913200
[Test build #33980 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33980/consoleFull)
for PR 6577 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6577#issuecomment-107912886
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 suyanNone opened a pull request:
https://github.com/apache/spark/pull/6586
[SPARK-8044][CORE] Avoid to use directbuffer while reading or writing disk
level block
1. I found if we use getChannel to put or get data, it will create
DirectBuffer anyway, which is not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6499#issuecomment-107970256
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/6499#issuecomment-107970222
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/6499#issuecomment-107971211
[Test build #33985 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33985/consoleFull)
for PR 6499 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6499#issuecomment-107972623
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/6579#issuecomment-107972651
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/6587#issuecomment-107973972
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/6587#issuecomment-107974608
[Test build #33988 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33988/consoleFull)
for PR 6587 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6579#issuecomment-107976125
[Test build #33989 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33989/consoleFull)
for PR 6579 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6583#issuecomment-107976638
[Test build #33981 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33981/consoleFull)
for PR 6583 at commit
GitHub user zsxwing opened a pull request:
https://github.com/apache/spark/pull/6588
[SPARK-3586][streaming]Support nested directories in Spark Streaming
Closes #2765
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zsxwing/spark
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6588#issuecomment-107978473
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/6499#issuecomment-107970783
[Test build #33985 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33985/consoleFull)
for PR 6499 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6499#issuecomment-107972650
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/6579#issuecomment-107972824
[Test build #33986 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33986/consoleFull)
for PR 6579 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6587#issuecomment-107974023
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 chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/5880#issuecomment-107977413
Oh, thanks for noticing this. But the answer is not necessary!
In user application, the `HiveContext` will create the `SessionState`
(indirectly) before
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6584#issuecomment-107979715
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/6586#issuecomment-107964631
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
601 - 700 of 893 matches
Mail list logo
