Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5830#issuecomment-100757536
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5830#issuecomment-100757539
Test FAILed.
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/5830#issuecomment-100757528
[Test build #32367 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32367/consoleFull)
for PR 5830 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6044#issuecomment-100763970
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/6044#issuecomment-100763963
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/5868#issuecomment-100764933
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/5868#issuecomment-100764931
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/5868#issuecomment-100764898
[Test build #32363 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32363/consoleFull)
for PR 5868 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5526#issuecomment-100771563
Test FAILed.
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/5526#issuecomment-100771540
[Test build #32365 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32365/consoleFull)
for PR 5526 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5526#issuecomment-100771558
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/5868#issuecomment-100756503
Update: I overlooked a missing `readFully`; my bad.
---
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 liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/5526#discussion_r30012303
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/sources/interfaces.scala ---
@@ -207,3 +246,218 @@ trait InsertableRelation {
trait
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/6048#issuecomment-100758572
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6048#issuecomment-100758661
[Test build #32368 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32368/consoleFull)
for PR 6048 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6047#issuecomment-100763206
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/5830#issuecomment-100763085
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/5830#issuecomment-100763215
[Test build #32371 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32371/consoleFull)
for PR 5830 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6047#issuecomment-100763207
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/6047#issuecomment-100763201
[Test build #32362 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32362/consoleFull)
for PR 6047 at commit
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/6044#issuecomment-100763734
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/5798#issuecomment-100764353
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/5798#issuecomment-100764345
**[Test build #32361 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32361/consoleFull)**
for PR 5798 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5798#issuecomment-100764355
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/5798#issuecomment-100767039
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/6019#issuecomment-100766990
@jkbradley If a Param is identified by the parents' uid and its name,
`Param.toString` shouldn't output the default value and user-supplied value for
a particular
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5447#issuecomment-100755705
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/5830#issuecomment-100756728
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/6048#issuecomment-100756980
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/6033#issuecomment-100756998
Thanks for adding this. Just so I understand, was the previous behavior
that these exceptions were silently swallowed? Or did they managed to get
logged somewhere
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5830#issuecomment-100756920
[Test build #32367 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32367/consoleFull)
for PR 5830 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5830#issuecomment-100756722
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6048#issuecomment-100756966
[Test build #32366 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32366/consoleFull)
for PR 6048 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6048#issuecomment-100756982
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/6044#issuecomment-100759905
Test FAILed.
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/5830#issuecomment-100760281
[Test build #32370 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32370/consoleFull)
for PR 5830 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5830#issuecomment-100763033
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/5830#issuecomment-100760284
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/5830#issuecomment-100760283
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5798#issuecomment-100767191
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/5798#issuecomment-100767199
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/5868#issuecomment-100767190
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/5868#issuecomment-100767198
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 mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/6045#discussion_r30013800
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/classification/LogisticRegression.scala
---
@@ -488,10 +488,19 @@ private class LogisticAggregator(
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/6045#discussion_r30013804
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/classification/LogisticRegressionSuite.scala
---
@@ -234,11 +236,22 @@ class LogisticRegressionSuite
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/6045#discussion_r30013806
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/classification/LogisticRegressionSuite.scala
---
@@ -266,12 +279,31 @@ class LogisticRegressionSuite
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/6045#discussion_r30013803
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/classification/LogisticRegressionSuite.scala
---
@@ -234,11 +236,22 @@ class LogisticRegressionSuite
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6039#issuecomment-100775532
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/6039#issuecomment-100775522
[Test build #32369 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32369/consoleFull)
for PR 6039 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6039#issuecomment-100775530
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 srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/6029#discussion_r30005639
--- Diff:
yarn/src/main/scala/org/apache/spark/deploy/yarn/ApplicationMaster.scala ---
@@ -573,10 +573,19 @@ object ApplicationMaster extends Logging {
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/5868#discussion_r30007379
--- Diff:
core/src/main/java/org/apache/spark/shuffle/unsafe/PackedRecordPointer.java ---
@@ -0,0 +1,74 @@
+/*
+ * Licensed to the Apache Software
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5868#issuecomment-100715431
Test FAILed.
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/5868#issuecomment-100715427
[Test build #32353 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32353/consoleFull)
for PR 5868 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5963#issuecomment-100720503
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/5963#issuecomment-100720496
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 dbtsai opened a pull request:
https://github.com/apache/spark/pull/6045
[SPARK-7518][ML] Tests for comparing probability and prediction in binary
logistic regression against R
Adding more tests for comparing probability and prediction in binary
logistic regression
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6045#issuecomment-100724403
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/6045#issuecomment-100724417
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/5886#issuecomment-100732126
[Test build #32359 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32359/consoleFull)
for PR 5886 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5886#issuecomment-100732031
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 this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5886#issuecomment-100732023
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 have
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/5963#issuecomment-100741355
@marmbrus @yhuai Any more comments?
---
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 zzcclp commented on the pull request:
https://github.com/apache/spark/pull/4805#issuecomment-100752171
Hi @koeninger , of cource, I can read kafka offset from ZK when recovering
by myself, I just want to know that writing to ZK is built-in support or not.
---
If your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6048#issuecomment-100756254
[Test build #32366 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32366/consoleFull)
for PR 6048 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5830#issuecomment-100760199
[Test build #32370 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32370/consoleFull)
for PR 5830 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5830#issuecomment-100760156
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/5830#issuecomment-100760162
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 yinxusen commented on the pull request:
https://github.com/apache/spark/pull/5980#issuecomment-100764274
@jkbradley Yes, thanks! Sorry for the delay 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6044#issuecomment-100777209
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/6044#issuecomment-100777124
[Test build #32372 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32372/consoleFull)
for PR 6044 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6044#issuecomment-100777217
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/6048#issuecomment-100756151
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/6048#issuecomment-100756159
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 tianyi opened a pull request:
https://github.com/apache/spark/pull/6048
[SPARK-7519][SQL] fix minor bugs in thrift server UI
Bugs description:
1. There are extra commas on the top of session list.
2. The format of time in Start at: part is not the same as
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6039#issuecomment-100759270
[Test build #32369 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32369/consoleFull)
for PR 6039 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6039#issuecomment-100759239
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/6039#issuecomment-100759233
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6044#issuecomment-100764093
[Test build #32372 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32372/consoleFull)
for PR 6044 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5868#issuecomment-100767584
[Test build #32373 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32373/consoleFull)
for PR 5868 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5798#issuecomment-100767572
[Test build #32374 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32374/consoleFull)
for PR 5798 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5830#issuecomment-100772474
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5830#issuecomment-100772478
Test FAILed.
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/5830#issuecomment-100772448
[Test build #32371 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32371/consoleFull)
for PR 5830 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5447#issuecomment-100755695
[Test build #32360 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32360/consoleFull)
for PR 5447 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5447#issuecomment-100755706
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/5886#issuecomment-100755821
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/5886#issuecomment-100755814
[Test build #32359 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32359/consoleFull)
for PR 5886 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5886#issuecomment-100755820
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 does
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6048#issuecomment-100758556
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/6048#issuecomment-100758615
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/6043#issuecomment-100757970
What about having the configs be under `managedMemory` but having the
internal package name be `managed`? That's my personal preference.
---
If your project is set
Github user tianyi commented on the pull request:
https://github.com/apache/spark/pull/6048#issuecomment-100758057
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6044#issuecomment-100759904
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/6044#issuecomment-100759902
[Test build #32364 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32364/consoleFull)
for PR 6044 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6043#issuecomment-100704094
[Test build #32350 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32350/consoleFull)
for PR 6043 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6043#issuecomment-100704097
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/6043#issuecomment-100704098
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/5868#issuecomment-100704454
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/5868#issuecomment-100704443
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
1 - 100 of 406 matches
Mail list logo
