You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2016/12/06 01:26:58 UTC
[jira] [Commented] (SPARK-18730) Ask the build script to link to
Jenkins test report page instead of full console output page when posting
to GitHub
[ https://issues.apache.org/jira/browse/SPARK-18730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15723958#comment-15723958 ]
Apache Spark commented on SPARK-18730:
--------------------------------------
User 'liancheng' has created a pull request for this issue:
https://github.com/apache/spark/pull/16163
> Ask the build script to link to Jenkins test report page instead of full console output page when posting to GitHub
> -------------------------------------------------------------------------------------------------------------------
>
> Key: SPARK-18730
> URL: https://issues.apache.org/jira/browse/SPARK-18730
> Project: Spark
> Issue Type: Bug
> Components: Build
> Reporter: Cheng Lian
> Assignee: Cheng Lian
> Priority: Minor
>
> Currently, the full console output page of a Spark Jenkins PR build can be as large as several megabytes. It takes a relatively long time to load and may even freeze the browser for quite a while.
> I'd suggest posting the test report page link to GitHub instead, which is way more concise and is usually the first page I'd like to check when investigating a Jenkins build failure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org