Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4778#issuecomment-76335376
[Test build #28047 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28047/consoleFull)
for PR 4778 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4778#issuecomment-76346385
[Test build #28047 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28047/consoleFull)
for PR 4778 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4778#issuecomment-76346390
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/4778#issuecomment-76346651
Ok LGTM merging into master 1.3 thanks @elyast
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/4778
---
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 andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/4778#discussion_r25472682
--- Diff:
core/src/test/scala/org/apache/spark/deploy/history/HistoryServerSuite.scala ---
@@ -0,0 +1,53 @@
+/*
+ * Licensed to the Apache
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4778#issuecomment-76153635
[Test build #27998 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27998/consoleFull)
for PR 4778 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/4778#issuecomment-76153038
ok to test
---
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 srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/4778#discussion_r25421061
--- Diff:
core/src/test/scala/org/apache/spark/deploy/history/HistoryServerSuite.scala ---
@@ -0,0 +1,53 @@
+/*
+ * Licensed to the Apache Software
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4778#issuecomment-76163934
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/4778#issuecomment-76163920
[Test build #27998 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27998/consoleFull)
for PR 4778 at commit
Github user elyast commented on a diff in the pull request:
https://github.com/apache/spark/pull/4778#discussion_r25488122
--- Diff:
core/src/test/scala/org/apache/spark/deploy/history/HistoryServerSuite.scala ---
@@ -0,0 +1,53 @@
+/*
+ * Licensed to the Apache Software
Github user elyast commented on a diff in the pull request:
https://github.com/apache/spark/pull/4778#discussion_r25488124
--- Diff:
core/src/test/scala/org/apache/spark/deploy/history/HistoryServerSuite.scala ---
@@ -0,0 +1,53 @@
+/*
+ * Licensed to the Apache Software
GitHub user elyast opened a pull request:
https://github.com/apache/spark/pull/4778
SPARK-2168 [Spark core] Use relative URIs for the app links in the History
Server.
As agreed in PR #1160 adding test to verify if history server generates
relative links to applications.
You can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4778#issuecomment-76120156
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 elyast commented on the pull request:
https://github.com/apache/spark/pull/1160#issuecomment-73587979
Fine with me, I will add tests on master with new PR
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user elyast closed the pull request at:
https://github.com/apache/spark/pull/1160
---
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/1160#issuecomment-73493001
Is this still live? I think this PR should be closed in any event, but the
test can go in master in a separate PR. Otherwise let's close this.
---
If your project is set
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1160#issuecomment-69217006
Looks like branch-1.0 is consistently failing tests (not related to this PR)
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1160#issuecomment-69131210
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/1160#issuecomment-69131206
[Test build #25194 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/25194/consoleFull)
for PR 1160 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1160#issuecomment-69111433
Actually, let's 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
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1160#issuecomment-69111397
I see. Nevertheless it would be good to merge the tests in master too. Feel
free to open a new PR just for the test.
---
If your project is set up for it, you can
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1160#issuecomment-69111523
[Test build #25182 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/25182/consoleFull)
for PR 1160 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1160#issuecomment-69118536
[Test build #25182 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/25182/consoleFull)
for PR 1160 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1160#issuecomment-69118543
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1160#issuecomment-69126243
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 have this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1160#issuecomment-69126536
[Test build #25194 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/25194/consoleFull)
for PR 1160 at commit
Github user elyast commented on the pull request:
https://github.com/apache/spark/pull/1160#issuecomment-68077764
@andrewor14 I think it's been fixed on master branch, so if you don't want
to release maintenance release for 1.0.x then I would suggest to close it.
---
If your project
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1160#issuecomment-67899124
Hey @elyast could you open this against the master branch? It would be good
if the latest Spark releases benefit from the changes here as well. For now, I
would
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1160#issuecomment-54694655
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
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1160#issuecomment-54697604
ok to test...
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1160#issuecomment-54698950
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19883/consoleFull)
for PR 1160 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1160#issuecomment-54700622
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19883/consoleFull)
for PR 1160 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1160#issuecomment-53341199
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 this
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/1160#discussion_r16683582
--- Diff:
core/src/test/scala/org/apache/spark/deploy/history/HistoryServerSuite.scala ---
@@ -0,0 +1,52 @@
+/*
+ * Licensed to the Apache
Github user elyast commented on a diff in the pull request:
https://github.com/apache/spark/pull/1160#discussion_r16685916
--- Diff:
core/src/test/scala/org/apache/spark/deploy/history/HistoryServerSuite.scala ---
@@ -0,0 +1,52 @@
+/*
+ * Licensed to the Apache Software
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/1160#issuecomment-47292613
Haven't looked at the code yet, but could you add a more descriptive title
to the PR? Thanks!
---
If your project is set up for it, you can reply to this email and have
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/1160#issuecomment-47292702
Also, this should probably go into master before it goes to branch-1.0.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user elyast commented on the pull request:
https://github.com/apache/spark/pull/1160#issuecomment-47294490
I have added more descriptive title
---
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
Github user elyast commented on the pull request:
https://github.com/apache/spark/pull/1160#issuecomment-47294545
so should I open another PR for master branch?
---
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/1160#issuecomment-47295405
There's a typo in your title. :-)
Also, it could be shorter. Think that the PR title becomes the summary in
the final git commit, so it shows in commands like git
GitHub user elyast opened a pull request:
https://github.com/apache/spark/pull/1160
SPARK-2168 Spark core
Removing full URI leaving only relative path in link to the completed
application plus unit test
You can merge this pull request into a Git repository by running:
$ git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1160#issuecomment-46727469
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
44 matches
Mail list logo
