hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5069) add a Hadoop-centric junit test result listener
Date Thu, 12 Feb 2009 14:06:00 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672979#action_12672979
] 

Steve Loughran commented on HADOOP-5069:
----------------------------------------

other feature req: have the <title> of the report include a customisable test name,
hostname and timestamp. Instead of being Unit Test Results, be something like "Hadoop Core
Tests on node14 at 2008-02-11 24:32"

> add a Hadoop-centric junit test result listener
> -----------------------------------------------
>
>                 Key: HADOOP-5069
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5069
>             Project: Hadoop Core
>          Issue Type: New Feature
>          Components: test
>    Affects Versions: 0.21.0
>            Reporter: Steve Loughran
>            Priority: Minor
>
> People are encountering different problems with hadoop's unit tests, defects currently
being WONTFIX'd
> # HADOOP-5001 : Junit tests that time out don't write any test progress related logs
> # HADOOP-4721 : OOM in .TestSetupAndCleanupFailure
> There is a root cause here, the XmlResultFormatter of Ant buffers everything before writing
out a DOM. Too much logged: OOM and no output. Timeout: kill and no output.
> We could add a new logger class to hadoop and then push it back into Ant once we were
happy, or keep it separate if we had specific dependencies (like on hadoop-dfs API) that they
lacked. 
> Some ideas
> # stream XML to disk. We would have to put the test summary at the end; could use XSL
to generate HTML and the classic XML content
> # stream XHTML to disk. Makes it readable as you go along; makes the XSL work afterwards
harder.
> # push out results as records to a DFS. There's a problem here in that this needs to
be a different DFS from that you are testing, yet it needs to be compatible with the client.

> Item #3 would be interesting but doing it inside JUnit is too dangerous classpath and
config wise. Better to have Ant do the copy afterwards. What is needed then is a way to easily
append different tests to the same DFS file in a way that tools can analyse them all afterwards.
The copy is easy -add a new Ant resource for that- but the choice of format is trickier.
> Here's some work I did on this a couple of years back; I've not done much since then:
http://people.apache.org/~stevel/slides/distributed_testing_with_smartfrog_slides.pdf
> Is anyone else interested in exploring this? 

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


Mime
View raw message