Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7883#issuecomment-135130627
It seems fine to me, although let's re-test quickly to make sure nothing
has broken.
---
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/7883#issuecomment-135132979
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/8444#discussion_r38018765
--- Diff: python/pyspark/sql/readwriter.py ---
@@ -125,23 +131,33 @@ def load(self, path=None, format=None, schema=None,
**options):
@since(1.4)
Github user feynmanliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/7884#discussion_r38019771
--- Diff: project/MimaExcludes.scala ---
@@ -60,6 +60,10 @@ object MimaExcludes {
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/8437#issuecomment-135136137
I would be okay just marking the whole test as ExtendedHiveTest.
Easy enough (good thing I made that change in a single commit).
---
If your project is set up
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8437#issuecomment-135142285
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/8398#issuecomment-135142271
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/8398#issuecomment-135142299
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/8465#issuecomment-135144393
[Test build #41643 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41643/console)
for PR 8465 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8466#issuecomment-135149638
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/8437#issuecomment-135149653
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/8466#issuecomment-135149636
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/8437#issuecomment-135149621
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/7494#issuecomment-135131987
[Test build #41629 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41629/console)
for PR 7494 at commit
Github user feynmanliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/7884#discussion_r38019508
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/classification/LogisticRegression.scala
---
@@ -833,14 +871,20 @@ private class LogisticCostFun(
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-135144791
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
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-135144862
K - I just sent a hotfix to up the timeout.
On Wed, Aug 26, 2015 at 9:51 AM, Marcelo Vanzin notificati...@github.com
wrote:
I'm working on fixing
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/8462#issuecomment-135149133
This should probably include some text documenting QR, with a brief
description and link to Wikipedia or other sources.
---
If your project is set up for it, you can
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8466#issuecomment-135149391
[Test build #41635 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41635/console)
for PR 8466 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8437#issuecomment-135128079
[Test build #41642 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41642/consoleFull)
for PR 8437 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8465#issuecomment-135129075
[Test build #41643 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41643/consoleFull)
for PR 8465 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7883#issuecomment-135130641
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7883#issuecomment-135132581
[Test build #41644 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41644/consoleFull)
for PR 7883 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8468#issuecomment-135136245
[Test build #1693 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1693/console)
for PR 8468 at commit
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/8452#issuecomment-135136204
LGTM. I'll merge with master and branch-1.5
---
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 tgravescs commented on the pull request:
https://github.com/apache/spark/pull/8398#issuecomment-135141921
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-135145694
[Test build #41647 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41647/consoleFull)
for PR 7629 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8465#issuecomment-135127618
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/8465#issuecomment-135127577
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/8468#issuecomment-135132266
Yeah, that's pretty trivial but OK. (As an aside, yeah I wish this markdown
was written with line breaks so the difference would be more obvious.)
---
If your project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8398#issuecomment-135142702
[Test build #41646 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41646/consoleFull)
for PR 8398 at commit
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/8437#issuecomment-135143652
SQL changes LGTM. I'll let @pwendell comment on build changes.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8437#issuecomment-135143411
[Test build #41645 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41645/consoleFull)
for PR 8437 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8462#issuecomment-135078514
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/8461#issuecomment-135078575
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/8461#issuecomment-135078620
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/8460#issuecomment-135080185
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/8461#issuecomment-135080196
[Test build #41630 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41630/consoleFull)
for PR 8461 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8460#issuecomment-135080189
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/8462#issuecomment-135078367
[Test build #41627 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41627/console)
for PR 8462 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8460#issuecomment-135079986
[Test build #41624 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41624/console)
for PR 8460 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8465#issuecomment-135099550
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/8465#issuecomment-135099613
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 squito opened a pull request:
https://github.com/apache/spark/pull/8466
[SPARK-10248] [core] track exceptions in dagscheduler event loop in tests
`DAGSchedulerEventLoop` normally only logs errors (so it can continue to
process more events, from other jobs). However,
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/8458#issuecomment-135108573
cc @davies
---
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 rotationsymmetry commented on a diff in the pull request:
https://github.com/apache/spark/pull/8022#discussion_r38008092
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/regression/StreamingDecay.scala ---
@@ -0,0 +1,57 @@
+/*
+ * Licensed to the Apache
Github user feynmanliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/8166#discussion_r38008775
--- Diff: python/pyspark/mllib/linalg/__init__.py ---
@@ -841,6 +930,41 @@ def parse(s):
def zeros(size):
return
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/7192#issuecomment-135118411
@cloud-fan can we close this pr? Thanks.
---
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 liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/8467#discussion_r38010586
--- Diff: docs/sql-programming-guide.md ---
@@ -1201,7 +1208,7 @@ saveDF(df1, data/test_table/key=1, parquet,
overwrite)
saveDF(df2,
Github user feynmanliang commented on the pull request:
https://github.com/apache/spark/pull/8241#issuecomment-135118506
@jkbradley and I talked offline, summary: lets make it `private[mllib]` and
clearly document in the trait's scaladoc that it's to prevent rebroadcasting
during
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8468#issuecomment-135130011
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7494#issuecomment-135132119
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/7494#issuecomment-135132120
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user feynmanliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/7884#discussion_r38018493
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/classification/LogisticRegression.scala
---
@@ -218,31 +217,59 @@ class LogisticRegression(override
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8452
---
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
Github user feynmanliang commented on the pull request:
https://github.com/apache/spark/pull/7884#issuecomment-135137091
Since `instances : RDD[(Double, Vector)]` is effectively processed as
`RDD[(Double, 1.0, Vector)]` (due to default params / method aliases for
`add`), I wonder if
Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/5636#discussion_r38021857
--- Diff:
core/src/test/scala/org/apache/spark/scheduler/DAGSchedulerSuite.scala ---
@@ -473,6 +473,280 @@ class DAGSchedulerSuite
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/8374#issuecomment-135141784
I don't think there is anything in conflict with implementing this in both
libraries. Really the redshift library is just a simplified version of this
since it only
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/8437#issuecomment-135129439
The `ExtendedHiveTest` tag looks good to me. I would consider dropping the
random smoke test part of things since we have lot of SQL tests and even hive
tests that
GitHub user moutai opened a pull request:
https://github.com/apache/spark/pull/8468
[DOCS][STREAMING][KAFKA]Fix typo in exactly once semantics
Fix Typo in exactly once semantics
[Semantics of output operations] link
You can merge this pull request into a Git repository by
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7883#issuecomment-135131291
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/7883#issuecomment-135131249
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/7883#issuecomment-135132975
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/7883#issuecomment-135132971
[Test build #41644 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41644/console)
for PR 7883 at commit
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/7883#issuecomment-135139768
Aha we did break them style rules in the last week ! -- @yu-iskw we can fix
them in this PR or a separate PR
---
If your project is set up for it, you can reply to
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8437#issuecomment-135142256
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/7629#issuecomment-135145221
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/7629#issuecomment-135145248
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/8437#issuecomment-135150079
[Test build #41648 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41648/consoleFull)
for PR 8437 at commit
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/8444#discussion_r38015686
--- Diff: python/pyspark/sql/readwriter.py ---
@@ -125,23 +131,33 @@ def load(self, path=None, format=None, schema=None,
**options):
@since(1.4)
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8468#issuecomment-135132690
[Test build #1693 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1693/consoleFull)
for PR 8468 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8453#issuecomment-135132832
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/8453#issuecomment-135132636
[Test build #41631 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41631/console)
for PR 8453 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8453#issuecomment-135132831
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 squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/8402#discussion_r38021708
--- Diff:
core/src/test/scala/org/apache/spark/scheduler/DAGSchedulerSuite.scala ---
@@ -695,6 +695,126 @@ class DAGSchedulerSuite
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8465#issuecomment-13513
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/8465#issuecomment-13516
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/8453#issuecomment-134846554
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/8453#issuecomment-134846595
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/8450#issuecomment-134867488
[Test build #41590 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41590/console)
for PR 8450 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7520#issuecomment-134872357
[Test build #41606 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41606/consoleFull)
for PR 7520 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8453#issuecomment-134847440
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/8453#issuecomment-134847441
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/8453#issuecomment-134847430
[Test build #41604 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41604/console)
for PR 8453 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8436#issuecomment-134847882
[Test build #41598 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41598/console)
for PR 8436 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8450#issuecomment-134867593
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134867614
Marcelo you will need to change the timeout in the code itself for it to
increase from 175
On Aug 25, 2015 11:24 PM, UCB AMPLab notificati...@github.com wrote:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8450#issuecomment-134867591
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/8436#issuecomment-134848568
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/8436#issuecomment-134848565
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/8453#issuecomment-134849228
[Test build #41605 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41605/consoleFull)
for PR 8453 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7520#issuecomment-134870294
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/7520#issuecomment-134870333
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/8445#issuecomment-134850439
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/8445#issuecomment-134850445
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/8445#issuecomment-134850117
[Test build #41600 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41600/console)
for PR 8445 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134854998
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/7629#issuecomment-134855001
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/7629#issuecomment-134854945
**[Test build #41584 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41584/console)**
for PR 7629 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8451#issuecomment-134860189
[Test build #41603 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41603/console)
for PR 8451 at commit
1 - 100 of 695 matches
Mail list logo
