Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1347
---
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/1347#issuecomment-48549409
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16484/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1347#issuecomment-48549406
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. I
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1347#issuecomment-48545318
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/1347#issuecomment-48545308
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/1347#issuecomment-48545241
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16479/
---
If your project is set up for it, you can
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/1347#issuecomment-48545276
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 this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1347#issuecomment-48545240
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 hav
Github user tmalaska commented on the pull request:
https://github.com/apache/spark/pull/1347#issuecomment-48536862
Yes let me figure that out now.
---
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/1347#issuecomment-48536758
Can you close the other PR?
---
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 th
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/1347#issuecomment-48536702
Naah, somethings are flaky in jenkins, cant be helped much. Hopefully this
will be done in another hour.
---
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/1347#issuecomment-48536454
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 tmalaska commented on the pull request:
https://github.com/apache/spark/pull/1347#issuecomment-48536448
Man I'm sorry this is taking so long. Thank you for your help.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/1347#issuecomment-48536362
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 this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1347#issuecomment-48536437
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 tdas commented on the pull request:
https://github.com/apache/spark/pull/1347#issuecomment-48536333
Jenkins, test this again.
---
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/1347#issuecomment-48536318
This looks like an unrelated error. Running the test again.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1347#issuecomment-48535195
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 hav
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1347#issuecomment-48535198
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16475/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1347#issuecomment-48524144
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/1347#issuecomment-48524160
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 tdas commented on the pull request:
https://github.com/apache/spark/pull/1347#issuecomment-48523902
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 this
GitHub user tdas opened a pull request:
https://github.com/apache/spark/pull/1347
[SPARK-1478].3: Upgrade FlumeInputDStream's FlumeReceiver to support
FLUME-1915
This is a modified version of this PR
https://github.com/apache/spark/pull/1168 done by @tmalaska
Adds MIMA binary c
23 matches
Mail list logo
