Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-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 9EAD610550 for ; Tue, 26 Nov 2013 13:51:39 +0000 (UTC) Received: (qmail 74617 invoked by uid 500); 26 Nov 2013 13:51:38 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 74480 invoked by uid 500); 26 Nov 2013 13:51:36 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 74464 invoked by uid 99); 26 Nov 2013 13:51:35 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Nov 2013 13:51:35 +0000 Date: Tue, 26 Nov 2013 13:51:35 +0000 (UTC) From: "Hadoop QA (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-1301) Need to log the blacklist additions/removals when YarnSchedule#allocate MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13832594#comment-13832594 ] Hadoop QA commented on YARN-1301: --------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12615834/YARN-1301.3.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javadoc{color}. The javadoc tool did not generate any warning messages. {color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse. {color:green}+1 findbugs{color}. The patch does not introduce any 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 hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager. {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-YARN-Build/2533//testReport/ Console output: https://builds.apache.org/job/PreCommit-YARN-Build/2533//console This message is automatically generated. > Need to log the blacklist additions/removals when YarnSchedule#allocate > ----------------------------------------------------------------------- > > Key: YARN-1301 > URL: https://issues.apache.org/jira/browse/YARN-1301 > Project: Hadoop YARN > Issue Type: Bug > Reporter: Zhijie Shen > Assignee: Tsuyoshi OZAWA > Priority: Minor > Fix For: 2.3.0 > > Attachments: YARN-1301.1.patch, YARN-1301.2.patch, YARN-1301.3.patch > > > Now without the log, it's hard to debug whether blacklist is updated on the scheduler side or not -- This message was sent by Atlassian JIRA (v6.1#6144)