Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Sun, 20 Dec 2015 02:57:46 +0000 (UTC)
From: "Rohith Sharma K S (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12922932.1450415399000.77182.1450580266675@Atlassian.JIRA>
In-Reply-To: <JIRA.12922932.1450415399000@Atlassian.JIRA>
References: <JIRA.12922932.1450415399000@Atlassian.JIRA>
 <JIRA.12922932.1450415399821@arcas>
Subject: [jira] [Commented] (YARN-4478) [Umbrella] : Track all the Test
 failures in YARN
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/YARN-4478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15065611#comment-15065611 ] 

Rohith Sharma K S commented on YARN-4478:
-----------------------------------------

I agree that currently labels OR/AND components can be named as *Test*. 
Point of concern is when a QA report test failures , contributors/committers has to search for the test failures JIRA IDs and comment on their respective JIRA may be like "test failures are unrelated to this patch. test failure is tracked by YARN-xxxx" This is very paining task when there are multiple module test failures. Instead of remembering all the test failures JIRA, Umbrella JIRA would help to find easily.

> [Umbrella] : Track all the Test failures in YARN
> ------------------------------------------------
>
>                 Key: YARN-4478
>                 URL: https://issues.apache.org/jira/browse/YARN-4478
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: yarn
>            Reporter: Rohith Sharma K S
>
> Recently many test cases are failing either timed out or new bug fix caused impact. Many test faiures JIRA are raised and are in progress.
> This is to track all the test failures JIRA's


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)