Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11992#issuecomment-202329074
**[Test build #54307 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54307/consoleFull)**
for PR 11992 at commit
[`6eb7f0e`](https://gi
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11992#issuecomment-202328776
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 have th
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11992#issuecomment-202328719
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 a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11905#issuecomment-202326589
**[Test build #54306 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54306/consoleFull)**
for PR 11905 at commit
[`d5cba5c`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11578#issuecomment-202323127
**[Test build #54305 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54305/consoleFull)**
for PR 11578 at commit
[`b8e031b`](https://gi
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/11578#discussion_r57557833
--- Diff:
core/src/main/scala/org/apache/spark/util/random/RandomSampler.scala ---
@@ -107,21 +114,21 @@ class BernoulliCellSampler[T](lb: Double, ub: Double,
Github user maropu commented on the pull request:
https://github.com/apache/spark/pull/11720#issuecomment-202320267
cc: @rxin
---
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
enab
Github user devaraj-kavali closed the pull request at:
https://github.com/apache/spark/pull/11916
---
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 featur
Github user devaraj-kavali commented on the pull request:
https://github.com/apache/spark/pull/11916#issuecomment-202318900
I have moved these changes to the PR
https://github.com/apache/spark/pull/11996 for SPARK-10530. @tgravescs, please
have a look into https://github.com/apache/sp
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11957#issuecomment-202318706
**[Test build #54303 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54303/consoleFull)**
for PR 11957 at commit
[`afecd4a`](https://gi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11996#issuecomment-202318667
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11994#issuecomment-202318703
**[Test build #54304 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54304/consoleFull)**
for PR 11994 at commit
[`2b7c5b1`](https://gi
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/11926#issuecomment-202318627
The failed tests are due to another bug in `Expand` operator's constraints.
Submitted #11995 to fix it.
---
If your project is set up for it, you can reply to this emai
GitHub user devaraj-kavali opened a pull request:
https://github.com/apache/spark/pull/11996
[SPARK-10530] [CORE] Kill other task attempts when one taskattempt
belonging the same task is succeeded in speculation
## What changes were proposed in this pull request?
With this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11994#issuecomment-202318098
**[Test build #54302 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54302/consoleFull)**
for PR 11994 at commit
[`ccf70bf`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11994#issuecomment-202318106
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/11994#issuecomment-202318109
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/11994#issuecomment-202317726
**[Test build #54302 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54302/consoleFull)**
for PR 11994 at commit
[`ccf70bf`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11995#issuecomment-202316604
**[Test build #54301 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54301/consoleFull)**
for PR 11995 at commit
[`84821b4`](https://gi
GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/11995
[SPARK-14191][SQL] Fix Expand operator constraints
## What changes were proposed in this pull request?
JIRA: https://issues.apache.org/jira/browse/SPARK-14191
`Expand` operator now uses
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11994#issuecomment-202314290
**[Test build #54300 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54300/consoleFull)**
for PR 11994 at commit
[`ce73708`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11994#issuecomment-202314333
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/11994#issuecomment-202314329
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/11994#issuecomment-202310574
**[Test build #54300 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54300/consoleFull)**
for PR 11994 at commit
[`ce73708`](https://gi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11994#issuecomment-202300012
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/11994#issuecomment-20232
**[Test build #54299 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54299/consoleFull)**
for PR 11994 at commit
[`29bf76e`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11994#issuecomment-202300015
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/11994#issuecomment-202299526
**[Test build #54299 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54299/consoleFull)**
for PR 11994 at commit
[`29bf76e`](https://gi
GitHub user jerryshao opened a pull request:
https://github.com/apache/spark/pull/11994
[SPARK-14151] Expose metrics Source and Sink interface
## What changes were proposed in this pull request?
This patch tries to expose metrics Source and Sink interface for external
devel
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11720#issuecomment-202298857
**[Test build #54298 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54298/consoleFull)**
for PR 11720 at commit
[`8fb9a14`](https://gi
Github user ueshin commented on the pull request:
https://github.com/apache/spark/pull/11720#issuecomment-202298736
@maropu Thank you for your review.
I modified as you mentioned.
> do we get wrong answers from this kind of incorrect stage graphs?
I don't think thi
Github user rishabhbhardwaj closed the pull request at:
https://github.com/apache/spark/pull/11873
---
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 featu
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11954#issuecomment-202285595
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/11954#issuecomment-202285590
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/11954#issuecomment-202285200
**[Test build #54297 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54297/consoleFull)**
for PR 11954 at commit
[`fa94568`](https://g
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11973#issuecomment-202277999
In addition, to make this more robust towards future changes, we can also
just have the merge script read the content of the contributing.md and delete
the non-title phras
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11973#issuecomment-202273472
I'm against the change to remove the template and simply provide
instructions. The problem is that most prs don't follow things like this. I
think just having the merge sc
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11993#issuecomment-202270402
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/11993#issuecomment-202270399
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/11993#issuecomment-202269903
**[Test build #54296 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54296/consoleFull)**
for PR 11993 at commit
[`45f8e93`](https://g
901 - 940 of 940 matches
Mail list logo
