Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1128#issuecomment-54694658
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 project d
Github user luyi0619 commented on the pull request:
https://github.com/apache/spark/pull/1128#issuecomment-51358241
sure, thanks for your advice
---
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 hav
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/1128#issuecomment-76272711
@luyi0619 mind closing this PR? It sounds like this can be pursued in a new
PR.
---
If your project is set up for it, you can reply to this email and have your
reply appe
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1128
---
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 enab
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1128#issuecomment-63598672
cc @jegonzal can you take a look at this?
---
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 doe
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/1128#issuecomment-75435408
Is this a WontFix at this stage or needs another look from @ankurdave or
@jegonzal ?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user ankurdave commented on the pull request:
https://github.com/apache/spark/pull/1128#issuecomment-75450827
I talked to @jegonzal and it seems this is the correct thing to do. I'll
merge it pending Jenkins.
---
If your project is set up for it, you can reply to this email an
Github user ankurdave commented on the pull request:
https://github.com/apache/spark/pull/1128#issuecomment-75450836
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1128#issuecomment-75451078
[Test build #27840 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27840/consoleFull)
for PR 1128 at commit
[`6f055f9`](https://githu
Github user ankurdave commented on the pull request:
https://github.com/apache/spark/pull/1128#issuecomment-75451786
Oh, this PR was against the old version of static PageRank that used
Pregel, while we now use a standalone implementation. I think it still has the
same problem and the
Github user jegonzal commented on the pull request:
https://github.com/apache/spark/pull/1128#issuecomment-75451894
Great! I agree with this proposal as well. I apologize for letting it sit
so long.
---
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/1128#issuecomment-75454846
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/27
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1128#issuecomment-75454845
[Test build #27840 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27840/consoleFull)
for PR 1128 at commit
[`6f055f9`](https://gith
13 matches
Mail list logo
