You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Hive QA (JIRA)" <ji...@apache.org> on 2013/11/01 04:12:19 UTC
[jira] [Commented] (HIVE-5708) PTest2 should trim long logs when
posting to jira
[ https://issues.apache.org/jira/browse/HIVE-5708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811001#comment-13811001 ]
Hive QA commented on HIVE-5708:
-------------------------------
{color:green}Overall{color}: +1 all checks pass
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12611398/HIVE-5708.patch
{color:green}SUCCESS:{color} +1 4547 tests passed
Test results: http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/94/testReport
Console output: http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/94/console
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}
This message is automatically generated.
> PTest2 should trim long logs when posting to jira
> -------------------------------------------------
>
> Key: HIVE-5708
> URL: https://issues.apache.org/jira/browse/HIVE-5708
> Project: Hive
> Issue Type: Improvement
> Reporter: Brock Noland
> Assignee: Brock Noland
> Priority: Minor
> Attachments: HIVE-5708.patch
>
>
> When a build fails we post the build log to JIRA. The issue is that sometimes this can be a couple hundred KB. Since this log is available in the link also mentioned in the JIRA we should trim the message size down to say *last* 200 lines and then add a warning when we need to.
--
This message was sent by Atlassian JIRA
(v6.1#6144)