Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6899
---
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 shivaram commented on the pull request:
https://github.com/apache/spark/pull/6899#issuecomment-114215239
Merging 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 not have this feature
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/6899#issuecomment-114197795
Yeah it should be fine to commit; go ahead.
Sent from my phone
> On Jun 22, 2015, at 1:25 AM, Sean Owen wrote:
>
> LGTM. This is safe to comm
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/6899#issuecomment-114037687
LGTM. This is safe to commit in that there was no actual test failure due
to this right?
---
If your project is set up for it, you can reply to this email and have your
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/6899#issuecomment-113842721
@davies @ahirreddy The tests here passed, but the test-selection logic was
_too_ good: by skipping all of the Scala / Java tests, we didn't write any
JUnit XML files,
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6899#issuecomment-113842319
[Test build #35374 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35374/console)
for PR 6899 at commit
[`4f4ea79`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6899#issuecomment-113842323
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/6899#issuecomment-113841800
[Test build #35374 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35374/consoleFull)
for PR 6899 at commit
[`4f4ea79`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6899#issuecomment-113841558
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/6899#issuecomment-113841562
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/6899#issuecomment-113840250
(Retesting to test a build script change)
---
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 proje
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/6899#issuecomment-113840219
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 h
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6899#issuecomment-113718188
[Test build #35354 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35354/console)
for PR 6899 at commit
[`4f4ea79`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6899#issuecomment-113718198
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/6899#issuecomment-113710138
[Test build #35354 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35354/consoleFull)
for PR 6899 at commit
[`4f4ea79`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6899#issuecomment-113710085
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/6899#issuecomment-113710082
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/6899#issuecomment-113709937
Jenkins, this is 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 h
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/6899#issuecomment-113605142
Jenkins, this is ok to test.
(So the Python style checks are run)
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user pradeepchhetri commented on the pull request:
https://github.com/apache/spark/pull/6899#issuecomment-113604222
@JoshRosen Thank you for reminding it. Added t2.large as well.
---
If your project is set up for it, you can reply to this email and have your
reply appear on Git
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/6899#issuecomment-113588384
We might as well include the new Tc.large instance while we're at it:
https://aws.amazon.com/blogs/aws/new-t2-large-instances/
---
If your project is set up for it, y
Github user pradeepchhetri commented on the pull request:
https://github.com/apache/spark/pull/6899#issuecomment-113583343
@srowen I created a JIRA ticket and updated the title with that.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
22 matches
Mail list logo
