Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9282#issuecomment-151209819
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 sethah commented on the pull request:
https://github.com/apache/spark/pull/9003#issuecomment-151211786
@mengxr Corrected `variance` to yield the population variance. Tests should
pass now.
---
If your project is set up for it, you can reply to this email and have your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9003#issuecomment-151212601
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 ehsanmok commented on the pull request:
https://github.com/apache/spark/pull/8729#issuecomment-151214114
@yu-iskw Thanks for your kind suggestions. Sure, I am going to do that asap.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9012#issuecomment-151213958
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/9281#issuecomment-151215897
I see the point, but, this is also not how the release tarballs are build.
Look at `release-build.sh`. I wouldn't mind adding more of the flags you see in
the releases,
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9258#issuecomment-151196146
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9281#issuecomment-151195397
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 charyorde commented on the pull request:
https://github.com/apache/spark/pull/8948#issuecomment-151197525
Is this fix in v1.5.2-rc1?
---
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/8093#issuecomment-151196859
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/8093#issuecomment-151196890
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/8093#issuecomment-151200883
**[Test build #44362 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44362/consoleFull)**
for PR 8093 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8093#issuecomment-151201802
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/8093#issuecomment-151201793
**[Test build #44362 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44362/consoleFull)**
for PR 8093 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9281#issuecomment-151205055
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/9012#issuecomment-151211346
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/9282#issuecomment-151212320
**[Test build #44364 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44364/consoleFull)**
for PR 9282 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9003#issuecomment-151213216
**[Test build #44366 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44366/consoleFull)**
for PR 9003 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9012#issuecomment-151213953
**[Test build #44365 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44365/consoleFull)**
for PR 9012 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9012#issuecomment-151213961
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9012#issuecomment-151215341
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/9012#issuecomment-151215364
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 kaysoky commented on the pull request:
https://github.com/apache/spark/pull/9282#issuecomment-151240433
:+1:
Tested on a local Mesos cluster (fine-grained mode).
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9281#issuecomment-151240734
**[Test build #44372 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44372/consoleFull)**
for PR 9281 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9281#issuecomment-151241000
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9281#issuecomment-151241009
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9281#issuecomment-151241007
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/9280#issuecomment-151243088
**[Test build #44363 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44363/consoleFull)**
for PR 9280 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9258#issuecomment-151231061
**[Test build #44360 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44360/consoleFull)**
for PR 9258 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9258#issuecomment-151231407
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9258#issuecomment-151231402
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/9281#issuecomment-151235901
**[Test build #44372 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44372/consoleFull)**
for PR 9281 at commit
Github user FRosner commented on the pull request:
https://github.com/apache/spark/pull/9222#issuecomment-151236579
In my opinion we are good to go if there are no objections from your side.
--
Sent from my phone. Please excuse my brevity.
Shivaram Venkataraman
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9283#issuecomment-151232108
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9283#issuecomment-151231763
**[Test build #44371 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44371/consoleFull)**
for PR 9283 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9283#issuecomment-151232104
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/9281#issuecomment-151232646
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 kayousterhout commented on a diff in the pull request:
https://github.com/apache/spark/pull/9273#discussion_r43032139
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/SparkDeploySchedulerBackend.scala
---
@@ -137,7 +137,7 @@ private[spark] class
601 - 638 of 638 matches
Mail list logo
