Github user uncleGen closed the pull request at:
https://github.com/apache/spark/pull/3768
---
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/3768#issuecomment-70392612
I've merged this into `branch-1.1` (1.1.2). Now that this is merged, do
you mind closing this PR (GitHub can't auto-close PRs that are opened against
maintenance
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/3768#issuecomment-70147186
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 uncleGen commented on the pull request:
https://github.com/apache/spark/pull/3768#issuecomment-70198185
@JoshRosen OKï¼ thank youï¼
---
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/3768#issuecomment-70147381
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/25610/consoleFull)
for PR 3768 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/3768#issuecomment-68813235
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/3768#issuecomment-68813622
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/25080/consoleFull)
for PR 3768 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3768#issuecomment-68818962
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/3768#issuecomment-68818953
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/25080/consoleFull)
for PR 3768 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/3768#issuecomment-68376638
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/3768#issuecomment-68376710
LGTM, pending Jenkins.
---
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/3768#issuecomment-68377078
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24899/consoleFull)
for PR 3768 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3768#issuecomment-68377345
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24899/consoleFull)
for PR 3768 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3768#issuecomment-68377346
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/3768#issuecomment-68380658
That latest failure is my fault (bad merge that I've reverted).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/3768#issuecomment-68380668
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/3768#issuecomment-68380897
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24900/consoleFull)
for PR 3768 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3768#issuecomment-68388202
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/3768#issuecomment-68388198
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24900/consoleFull)
for PR 3768 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/3768#issuecomment-67988310
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/3768#issuecomment-67988843
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24745/consoleFull)
for PR 3768 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3768#issuecomment-67996167
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24745/consoleFull)
for PR 3768 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3768#issuecomment-67996175
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/3768#issuecomment-67996364
I agree that the test failure seems unrelated to this patch, but we should
definitely investigate it (maybe separately):
```
OK (skipped=1)
Traceback
GitHub user uncleGen opened a pull request:
https://github.com/apache/spark/pull/3768
[SPARK-4920][UI]: back port the PR-3763 to branch 1.1
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/uncleGen/spark branch-1.1-1223
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3768#issuecomment-67917552
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24721/consoleFull)
for PR 3768 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3768#issuecomment-67920211
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24721/consoleFull)
for PR 3768 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3768#issuecomment-67920215
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/3768#issuecomment-67922723
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24728/consoleFull)
for PR 3768 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3768#issuecomment-67925419
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24728/consoleFull)
for PR 3768 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3768#issuecomment-67925426
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user uncleGen commented on the pull request:
https://github.com/apache/spark/pull/3768#issuecomment-67926060
There are two irrelevant test failures.
---
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
32 matches
Mail list logo
