You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Konstantin Boudnik (JIRA)" <ji...@apache.org> on 2010/03/31 07:46:27 UTC

[jira] Created: (HADOOP-6666) Introduce common logging mechanism to mark begin and end of test cases execution

Introduce common logging mechanism to mark begin and end of test cases execution
--------------------------------------------------------------------------------

                 Key: HADOOP-6666
                 URL: https://issues.apache.org/jira/browse/HADOOP-6666
             Project: Hadoop Common
          Issue Type: Improvement
          Components: test
            Reporter: Konstantin Boudnik


It is pretty hard to diagnose a test problem (especially in Hudson) when all you have is a very long log file for all your tests output in one place.

ZOOKEEPER-724 seems to have a nice solution for this problem.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HADOOP-6666) Introduce common logging mechanism to mark begin and end of test cases execution

Posted by "Konstantin Boudnik (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-6666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konstantin Boudnik updated HADOOP-6666:
---------------------------------------

    Environment: Requires at least JUnit v. 4.8.1

> Introduce common logging mechanism to mark begin and end of test cases execution
> --------------------------------------------------------------------------------
>
>                 Key: HADOOP-6666
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6666
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: test
>         Environment: Requires at least JUnit v. 4.8.1
>            Reporter: Konstantin Boudnik
>
> It is pretty hard to diagnose a test problem (especially in Hudson) when all you have is a very long log file for all your tests output in one place.
> ZOOKEEPER-724 seems to have a nice solution for this problem.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.