Return-Path: X-Original-To: apmail-tajo-issues-archive@minotaur.apache.org Delivered-To: apmail-tajo-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 020A6105CE for ; Fri, 18 Apr 2014 08:37:27 +0000 (UTC) Received: (qmail 68170 invoked by uid 500); 18 Apr 2014 06:50:47 -0000 Delivered-To: apmail-tajo-issues-archive@tajo.apache.org Received: (qmail 68139 invoked by uid 500); 18 Apr 2014 06:50:46 -0000 Mailing-List: contact issues-help@tajo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@tajo.apache.org Delivered-To: mailing list issues@tajo.apache.org Received: (qmail 68131 invoked by uid 99); 18 Apr 2014 06:50:45 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Apr 2014 06:50:45 +0000 X-ASF-Spam-Status: No, hits=-2001.0 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.3] (HELO mail.apache.org) (140.211.11.3) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 18 Apr 2014 06:50:44 +0000 Received: (qmail 67562 invoked by uid 99); 18 Apr 2014 06:50:18 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Apr 2014 06:50:18 +0000 Date: Fri, 18 Apr 2014 06:50:18 +0000 (UTC) From: "Tajo QA (JIRA)" To: issues@tajo.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (TAJO-734) Arrange TajoCli output message. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/TAJO-734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973836#comment-13973836 ] Tajo QA commented on TAJO-734: ------------------------------ {color:red}*-1 overall.*{color} Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12640780/TAJO-734-4.patch against master revision 508ebed. {color:green}+1 @author.{color} The patch does not contain any @author tags. {color:green}+1 tests included.{color} The patch appears to include 2 new or modified test files. {color:green}+1 javac.{color} The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javadoc.{color} The applied patch does not increase the total number of javadoc warnings. {color:green}+1 checkstyle.{color} The patch generated 0 code style errors. {color:red}-1 findbugs.{color} The patch appears to introduce 196 new Findbugs (version 1.3.9) warnings. {color:green}+1 release audit.{color} The applied patch does not increase the total number of release audit warnings. {color:green}+1 core tests.{color} The patch passed unit tests in tajo-client tajo-common tajo-core/tajo-core-backend tajo-rpc. Test results: https://builds.apache.org/job/PreCommit-TAJO-Build/354//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-TAJO-Build/354//artifact/incubator-tajo/patchprocess/newPatchFindbugsWarningstajo-core-backend.html Console output: https://builds.apache.org/job/PreCommit-TAJO-Build/354//console This message is automatically generated. > Arrange TajoCli output message. > ------------------------------- > > Key: TAJO-734 > URL: https://issues.apache.org/jira/browse/TAJO-734 > Project: Tajo > Issue Type: Improvement > Reporter: hyoungjunkim > Assignee: hyoungjunkim > Priority: Minor > Attachments: TAJO-734-4.patch, TAJO-734.patch, TAJO-734_2.patch, TAJO_734_3.patch, TAJO_734_findbugs.patch > > > See title. TajoCli prints information and error message with various format. These message must be arranged because ETL program uses TajoCli's information or error message. -- This message was sent by Atlassian JIRA (v6.2#6252)