You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2016/04/22 19:42:13 UTC

[jira] [Commented] (YARN-4478) [Umbrella] : Track all the Test failures in YARN

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

Vinod Kumar Vavilapalli commented on YARN-4478:
-----------------------------------------------

bq. 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.
Actually I've tried adding more and more to this umbrella, but it is going out of hand.

I kind of agree with [~kasha], we will always have failing unit tests that need fixing. Let's just use the bug-type and component from on - those are easy to search for. I'm going to use ticket-type from now on, appreciate others also doing the same.

[~rohithsharma], let's use this umbrella for your current initiative and then close it down.

> [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)