HeartSaVioR commented on pull request #28841:
URL: https://github.com/apache/spark/pull/28841#issuecomment-729688337
I'll close this PR to avoid any confusion. Thanks again @cchighman for your
great contribution. I'll try my best to help getting this in.
HeartSaVioR commented on pull request #28841:
URL: https://github.com/apache/spark/pull/28841#issuecomment-729682457
I've submitted #30411 to take over this & address my own review comments.
This is an automated message from
HeartSaVioR commented on pull request #28841:
URL: https://github.com/apache/spark/pull/28841#issuecomment-729483537
Thanks @cchighman for great efforts during so far, and sorry to make you
struggle with the review process. I'll take this over based on the current
state of the PR and
HeartSaVioR commented on pull request #28841:
URL: https://github.com/apache/spark/pull/28841#issuecomment-725767057
The problem is feedback cycle, not whether @cchighman is busy or not. We are
requiring contributors for multiple months to keep on focus, whereas reviewers
don't promise
HeartSaVioR commented on pull request #28841:
URL: https://github.com/apache/spark/pull/28841#issuecomment-722675458
I see you update the PR. Thanks! As you're upmerging the branch instead of
rebasing it's uneasy to check the effective changes. Two questions:
1. Does your last
HeartSaVioR commented on pull request #28841:
URL: https://github.com/apache/spark/pull/28841#issuecomment-720900095
Sigh. Now it has conflicts so I can't go with giving +1 and merging.
@cchighman Could you please fix the conflicts? It would be totally OK if
you'd like to let me
HeartSaVioR commented on pull request #28841:
URL: https://github.com/apache/spark/pull/28841#issuecomment-715668416
I wouldn't request to an individual contributor doing the heavy work
consistently - now this PR has nearly 300 comments. If the remaining comments
are minors (not
HeartSaVioR commented on pull request #28841:
URL: https://github.com/apache/spark/pull/28841#issuecomment-703479408
@cchighman Gentle ping in case notice wasn't sent for my review comments.
This is an automated message from
HeartSaVioR commented on pull request #28841:
URL: https://github.com/apache/spark/pull/28841#issuecomment-693225135
retest this, please
This is an automated message from the Apache Git Service.
To respond to the message,
HeartSaVioR commented on pull request #28841:
URL: https://github.com/apache/spark/pull/28841#issuecomment-675301748
retest this, please
This is an automated message from the Apache Git Service.
To respond to the message,
HeartSaVioR commented on pull request #28841:
URL: https://github.com/apache/spark/pull/28841#issuecomment-666732439
> There are quite a bit of commits here. Would it be preferred if I
re-opened this PR for a cleaner merge to master?
Let's hear the voice on reopening the PR, as
HeartSaVioR commented on pull request #28841:
URL: https://github.com/apache/spark/pull/28841#issuecomment-664141747
I meant this build -
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/126567/testReport
The failed test from this build is the UT added here.
HeartSaVioR commented on pull request #28841:
URL: https://github.com/apache/spark/pull/28841#issuecomment-664059281
Test failure looks related.
This is an automated message from the Apache Git Service.
To respond to the
13 matches
Mail list logo