Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SPARK-2168 [Spark core] Use relative URIs for the app links in the History Server. #4778

Closed
wants to merge 3 commits into from

Conversation

elyast
Copy link
Contributor

@elyast elyast commented Feb 26, 2015

As agreed in PR #1160 adding test to verify if history server generates relative links to applications.

@AmplabJenkins
Copy link

Can one of the admins verify this patch?

@srowen
Copy link
Member

srowen commented Feb 26, 2015

ok to test

@SparkQA
Copy link

SparkQA commented Feb 26, 2015

Test build #27998 has started for PR 4778 at commit 6d7866d.

  • This patch merges cleanly.

@SparkQA
Copy link

SparkQA commented Feb 26, 2015

Test build #27998 has finished for PR 4778 at commit 6d7866d.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds the following public classes (experimental):
    • class HistoryServerSuite extends FunSuite with Matchers with MockitoSugar

@AmplabJenkins
Copy link

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/27998/
Test PASSed.

val response = page.render(request)

//then
val links = response \\ "a"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A bunch of little style nits: The indentation is off by one here. Also I think the imports could be ordered, with scala import first and separated by a line. Fix the extra space in true ) above. Don't we need to import postfixOps to avoid a compiler warning? Do the historyServer and request have to be members?

Otherwise this looks just fine as a follow-on test.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I compare indentation with FsHistoryProviderSuite and imho its the same, imports will do.
I don't think postfixOps is actually needed here. I will make historyServer and request local variables.

@SparkQA
Copy link

SparkQA commented Feb 27, 2015

Test build #28047 has started for PR 4778 at commit 0c07fab.

  • This patch merges cleanly.

@SparkQA
Copy link

SparkQA commented Feb 27, 2015

Test build #28047 has finished for PR 4778 at commit 0c07fab.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds the following public classes (experimental):
    • class HistoryServerSuite extends FunSuite with Matchers with MockitoSugar

@AmplabJenkins
Copy link

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/28047/
Test PASSed.

@andrewor14
Copy link
Contributor

Ok LGTM merging into master 1.3 thanks @elyast

@asfgit asfgit closed this in 4a8a0a8 Feb 27, 2015
asfgit pushed a commit that referenced this pull request Feb 27, 2015
…story Server.

As agreed in PR #1160 adding test to verify if history server generates relative links to applications.

Author: Lukasz Jastrzebski <[email protected]>

Closes #4778 from elyast/master and squashes the following commits:

0c07fab [Lukasz Jastrzebski] Incorporating comments for SPARK-2168
6d7866d [Lukasz Jastrzebski] Adjusting test for  SPARK-2168 for master branch
d6f4fbe [Lukasz Jastrzebski] Added test for  SPARK-2168

(cherry picked from commit 4a8a0a8)
Signed-off-by: Andrew Or <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants