Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10695#issuecomment-170598369
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10695#issuecomment-170598370
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10695#issuecomment-170598071
**[Test build #49147 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49147/consoleFull)**
for PR 10695 at commit
[`8f84ea4`](https://g
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/10685#issuecomment-170597277
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 f
Github user hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/10689#issuecomment-170597130
@gatorsmile I do see the performance benefits of ```limit``` while
processing. The reservation I am having is reasoning about non-toplevel
```limit``` statements. A
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10646#issuecomment-170596021
**[Test build #49152 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49152/consoleFull)**
for PR 10646 at commit
[`18091f7`](https://gi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10399#issuecomment-170594661
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10399#issuecomment-170594658
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10399#issuecomment-170594041
**[Test build #49145 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49145/consoleFull)**
for PR 10399 at commit
[`ed90585`](https://g
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/10646#issuecomment-170591130
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 thi
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/10689#issuecomment-170589671
@hvanhovell Let me share my two cents:
- We have another PR to push down `Limit` through `Union ALL`. However,
it is impossible to push `Limit` through `Union D
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10587#issuecomment-170587084
**[Test build #2364 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2364/consoleFull)**
for PR 10587 at commit
[`d045ea9`](https://
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10210#issuecomment-170585946
**[Test build #49151 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49151/consoleFull)**
for PR 10210 at commit
[`775c8e9`](https://gi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10685#issuecomment-170582183
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10685#issuecomment-170582188
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10685#issuecomment-170581952
**[Test build #49144 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49144/consoleFull)**
for PR 10685 at commit
[`0055761`](https://g
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10029#issuecomment-170578993
**[Test build #49150 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49150/consoleFull)**
for PR 10029 at commit
[`45d9f0c`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10210#issuecomment-170578737
**[Test build #49149 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49149/consoleFull)**
for PR 10210 at commit
[`4a41eb4`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10210#issuecomment-170578743
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10210#issuecomment-170578741
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10210#issuecomment-170578403
**[Test build #49149 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49149/consoleFull)**
for PR 10210 at commit
[`4a41eb4`](https://gi
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/10029#issuecomment-170578055
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 fe
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10029#issuecomment-170576891
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10029#issuecomment-170576801
**[Test build #49146 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49146/consoleFull)**
for PR 10029 at commit
[`45d9f0c`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10029#issuecomment-170576895
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/10699#discussion_r49327991
--- Diff: docs/running-on-yarn.md ---
@@ -260,10 +260,10 @@ If you need a reference to the proper location to put
log files in the YARN so t
(none)
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10699#issuecomment-170574209
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10699#issuecomment-170574029
**[Test build #49148 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49148/consoleFull)**
for PR 10699 at commit
[`f304363`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10699#issuecomment-170574208
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10699#issuecomment-170567981
**[Test build #49148 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49148/consoleFull)**
for PR 10699 at commit
[`f304363`](https://gi
GitHub user tgravescs opened a pull request:
https://github.com/apache/spark/pull/10699
[SPARK-2930] clarify docs on using webhdfs with spark.yarn.access.namâ¦
â¦enodes
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tgravescs/s
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10029#issuecomment-170563859
**[Test build #49146 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49146/consoleFull)**
for PR 10029 at commit
[`45d9f0c`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10399#issuecomment-170562802
**[Test build #49145 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49145/consoleFull)**
for PR 10399 at commit
[`ed90585`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10695#issuecomment-170562702
**[Test build #49147 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49147/consoleFull)**
for PR 10695 at commit
[`8f84ea4`](https://gi
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/10695#issuecomment-170558742
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 fe
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/10029#issuecomment-170558530
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 fe
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/10399#issuecomment-170558313
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 fe
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10587#issuecomment-170556401
**[Test build #2364 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2364/consoleFull)**
for PR 10587 at commit
[`d045ea9`](https://g
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10587#issuecomment-170555928
I can't imagine it's related as it's just a doc change, so must be flaky
tests, but let me just run it again
---
If your project is set up for it, you can reply to this
Github user aditanase commented on a diff in the pull request:
https://github.com/apache/spark/pull/10241#discussion_r49322343
--- Diff:
yarn/src/main/scala/org/apache/spark/deploy/yarn/YarnAllocator.scala ---
@@ -84,7 +84,19 @@ private[yarn] class YarnAllocator(
@volatile p
Github user yinxusen commented on the pull request:
https://github.com/apache/spark/pull/9971#issuecomment-170551583
Ping @jkbradley
---
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/10685#issuecomment-170551190
**[Test build #49144 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49144/consoleFull)**
for PR 10685 at commit
[`0055761`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10029#issuecomment-170550666
**[Test build #49128 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49128/consoleFull)**
for PR 10029 at commit
[`45d9f0c`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10029#issuecomment-170550776
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10029#issuecomment-170550777
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/10685#issuecomment-170550426
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 f
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10685#issuecomment-170549645
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10587#issuecomment-170549807
**[Test build #2363 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2363/consoleFull)**
for PR 10587 at commit
[`d045ea9`](https://
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10685#issuecomment-170549636
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10685#issuecomment-170549509
**[Test build #49138 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49138/consoleFull)**
for PR 10685 at commit
[`0055761`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10692#issuecomment-170545480
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10692#issuecomment-170545395
**[Test build #49116 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49116/consoleFull)**
for PR 10692 at commit
[`a3e3e17`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10692#issuecomment-170545478
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10399#issuecomment-170543092
**[Test build #49123 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49123/consoleFull)**
for PR 10399 at commit
[`ed90585`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10399#issuecomment-170543249
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10399#issuecomment-170543254
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10502#issuecomment-170542473
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10502#issuecomment-170542471
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10526#issuecomment-170542310
**[Test build #2362 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2362/consoleFull)**
for PR 10526 at commit
[`174b40f`](https://
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10502#issuecomment-170542317
**[Test build #49122 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49122/consoleFull)**
for PR 10502 at commit
[`dfc7506`](https://g
Github user Wenpei commented on the pull request:
https://github.com/apache/spark/pull/10587#issuecomment-170541326
@srowen Do you know what happened?
I check the failed log but don't know why. EVN issues?
---
If your project is set up for it, you can reply to this email and hav
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10698#issuecomment-170529156
Can one of the admins verify this patch?
---
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 jaceklaskowski opened a pull request:
https://github.com/apache/spark/pull/10698
[STREAMING][MINOR] Typo fixes
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jaceklaskowski/spark
streaming-kafka-typo-fixes
Alternat
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9971#issuecomment-170522536
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/9971#issuecomment-170522538
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9971#issuecomment-170522209
**[Test build #49140 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49140/consoleFull)**
for PR 9971 at commit
[`8c02be2`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10696#issuecomment-170519594
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10696#issuecomment-170519598
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10696#issuecomment-170519488
**[Test build #49135 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49135/consoleFull)**
for PR 10696 at commit
[`2d953bf`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10695#issuecomment-170519077
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10695#issuecomment-170519076
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10186#issuecomment-170516915
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10186#issuecomment-170516914
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10186#issuecomment-170516800
**[Test build #49141 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49141/consoleFull)**
for PR 10186 at commit
[`aa9d40f`](https://g
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10587#issuecomment-170516355
**[Test build #2363 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2363/consoleFull)**
for PR 10587 at commit
[`d045ea9`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10563#issuecomment-170515645
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 projec
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/10695#issuecomment-170515649
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 fe
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10563#issuecomment-170515641
**[Test build #49142 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49142/consoleFull)**
for PR 10563 at commit
[`50d4634`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10563#issuecomment-170515647
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10563#issuecomment-170514991
**[Test build #49142 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49142/consoleFull)**
for PR 10563 at commit
[`50d4634`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10587#issuecomment-170514576
**[Test build #2361 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2361/consoleFull)**
for PR 10587 at commit
[`d045ea9`](https://
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10563#issuecomment-170513357
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10186#issuecomment-170513220
**[Test build #49141 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49141/consoleFull)**
for PR 10186 at commit
[`aa9d40f`](https://gi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10563#issuecomment-170513355
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 projec
Github user yinxusen commented on the pull request:
https://github.com/apache/spark/pull/10186#issuecomment-170512065
Change the version to 2.2.0
---
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/10695#issuecomment-170511844
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10685#issuecomment-170512729
**[Test build #49138 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49138/consoleFull)**
for PR 10685 at commit
[`0055761`](https://gi
Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/9027#issuecomment-170512561
Discussions on the dev mailing list.
---
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 chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/10563#issuecomment-170512472
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9971#issuecomment-170512145
**[Test build #49140 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49140/consoleFull)**
for PR 9971 at commit
[`8c02be2`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10695#issuecomment-170511846
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user yinxusen commented on the pull request:
https://github.com/apache/spark/pull/9971#issuecomment-170511125
test it 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 featur
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10697#issuecomment-170510856
Can one of the admins verify this patch?
---
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 chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/10563#issuecomment-170510742
Weird, `scala/sbt ... scalastyle` doesn't report the scala style issue, but
Jenkins does.
---
If your project is set up for it, you can reply to this email and
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/10685#issuecomment-170510313
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 f
GitHub user Earthson opened a pull request:
https://github.com/apache/spark/pull/10697
[ML] ArrayType(_, true) should also accept ArrayType(_, false)
https://issues.apache.org/jira/browse/SPARK-12746
You can merge this pull request into a Git repository by running:
$ git pull h
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10563#issuecomment-170509968
**[Test build #49136 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49136/consoleFull)**
for PR 10563 at commit
[`6237aad`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10563#issuecomment-170509974
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10696#issuecomment-170510066
**[Test build #49135 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49135/consoleFull)**
for PR 10696 at commit
[`2d953bf`](https://gi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10563#issuecomment-170509970
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 projec
501 - 600 of 749 matches
Mail list logo
