Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/6939#issuecomment-120882412
Since https://github.com/apache/spark/pull/6830 is merged and this passes,
anyone object to merging?
---
If your project is set up for it, you can reply to this email
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/6939#issuecomment-121061861
LGTM, since all scala/java/python tests pass, this is good to go. I am
merging this to master.
---
If your project is set up for it, you can reply to this email and have
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/6939#issuecomment-121064168
Hey @harishreedharan i have merged this. Somehow this PR was not closed
automatically. Can you close it?
---
If your project is set up for it, you can reply to this email
Github user harishreedharan closed the pull request at:
https://github.com/apache/spark/pull/6939
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6939#issuecomment-120779686
[Test build #1045 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1045/console)
for PR 6939 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6939#issuecomment-120771756
[Test build #1045 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1045/consoleFull)
for PR 6939 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6939#issuecomment-120706909
[Test build #1043 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1043/console)
for PR 6939 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6939#issuecomment-120701936
[Test build #1043 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1043/consoleFull)
for PR 6939 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6939#issuecomment-120719527
[Test build #1044 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1044/consoleFull)
for PR 6939 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6939#issuecomment-120728603
[Test build #1044 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1044/console)
for PR 6939 at commit
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/6939#issuecomment-120498860
@harishreedharan Will fix the flaky test by #7344
---
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/6939#issuecomment-120199464
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 tdas commented on the pull request:
https://github.com/apache/spark/pull/6939#issuecomment-120199419
Jenkins, test this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6939#issuecomment-120199479
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/6939#issuecomment-120216522
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 harishreedharan commented on the pull request:
https://github.com/apache/spark/pull/6939#issuecomment-120221528
This pyspark test has been failing all over:
```
==
FAIL: test_time_with_timezone
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6939#issuecomment-120216505
[Test build #36990 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36990/console)
for PR 6939 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6939#issuecomment-120199814
[Test build #36990 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36990/consoleFull)
for PR 6939 at commit
Github user harishreedharan commented on the pull request:
https://github.com/apache/spark/pull/6939#issuecomment-118987352
ping @tdas
---
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 tdas commented on the pull request:
https://github.com/apache/spark/pull/6939#issuecomment-117544502
I will wait for the #6830 to be merged which is more contentious. Some
things may need to be updated in this PR if there are conflicts. And then we
will be able to run
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/6939#issuecomment-117159663
Ping @harishreedharan I am sure you wouldn't propose this otherwise, but,
just wanted to understand what if any potential incompatibilities this entails,
particularly
Github user harishreedharan commented on the pull request:
https://github.com/apache/spark/pull/6939#issuecomment-117434018
I am on vacation till Sunday. Please feel free to merge this - if I have
any concerns at that time I will make some noise.
On Tuesday, June 30, 2015,
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/6939#issuecomment-114481793
This is probably fine, but are there any potential incompatibilities or
significant differences between the two that would affect any users? might be
worth a scan
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6939#issuecomment-114252826
[Test build #35484 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35484/consoleFull)
for PR 6939 at commit
GitHub user harishreedharan opened a pull request:
https://github.com/apache/spark/pull/6939
[SPARK-8533][Streaming] Upgrade Flume to 1.6.0
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/harishreedharan/spark
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6939#issuecomment-114292775
[Test build #35484 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35484/console)
for PR 6939 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6939#issuecomment-114292802
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/6939#issuecomment-114251212
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/6939#issuecomment-114251307
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
29 matches
Mail list logo
