You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Owen O'Malley (JIRA)" <ji...@apache.org> on 2007/04/13 19:25:15 UTC
[jira] Created: (HADOOP-1257) a distributed junit test runner
a distributed junit test runner
-------------------------------
Key: HADOOP-1257
URL: https://issues.apache.org/jira/browse/HADOOP-1257
Project: Hadoop
Issue Type: New Feature
Components: test
Affects Versions: 0.12.3
Reporter: Owen O'Malley
Assigned To: Owen O'Malley
It would be nice to have a distributed junit runner that would run 100 instances of each test a separate map, and use counters to count how many times each test passed/failed/hung.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Created: (HADOOP-1257) a distributed junit test runner
Posted by Nigel Daley <nd...@yahoo-inc.com>.
Tom, haven't you done something similar with your https://
computefarm.dev.java.net/ project?
On Apr 13, 2007, at 10:25 AM, Owen O'Malley (JIRA) wrote:
> a distributed junit test runner
> -------------------------------
>
> Key: HADOOP-1257
> URL: https://issues.apache.org/jira/browse/
> HADOOP-1257
> Project: Hadoop
> Issue Type: New Feature
> Components: test
> Affects Versions: 0.12.3
> Reporter: Owen O'Malley
> Assigned To: Owen O'Malley
>
>
> It would be nice to have a distributed junit runner that would run
> 100 instances of each test a separate map, and use counters to
> count how many times each test passed/failed/hung.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
[jira] Commented: (HADOOP-1257) a distributed junit test runner
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488730 ]
Doug Cutting commented on HADOOP-1257:
--------------------------------------
Bootstrapping could be a little complicated here: do we use an older version of Hadoop to test the new version? Since Hudson runs on a 4-processor box, we might get some mileage by simply getting junit tests to run in parallel. Ant's parallel task is almost appropriate, except there's no easy way I can see to get each junit test to be a sub-task of a parallel task. But perhaps a simple parallel-junit task could be written for this. Test could still be run in separate JVMs, and we could run as many at once as there are CPUs (a feature of the parallel task). A 4x speedup would be very welcome!
> a distributed junit test runner
> -------------------------------
>
> Key: HADOOP-1257
> URL: https://issues.apache.org/jira/browse/HADOOP-1257
> Project: Hadoop
> Issue Type: New Feature
> Components: test
> Affects Versions: 0.12.3
> Reporter: Owen O'Malley
> Assigned To: Owen O'Malley
>
> It would be nice to have a distributed junit runner that would run 100 instances of each test a separate map, and use counters to count how many times each test passed/failed/hung.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-1257) a distributed junit test runner
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489098 ]
Tom White commented on HADOOP-1257:
-----------------------------------
> Tom, haven't you done something similar with your https://
> computefarm.dev.java.net/ project?
Yes, this was some time ago now, but the basic idea was to extend JUnit (this in itself was hard since JUnit 3 was not really written for extensibility :) to distribute test cases to worker machines using JavaSpaces. The idea was to distribute them in order to get the whole suite to run faster, not to run each test a number of times in order to examine failure rates.
One of the nice things was that you didn't have to install your tests on the workers since Jini code mobility ensured the bytecodes were downloaded as necessary. However you did need to make sure your tests were Serializable... More at https://computefarm.dev.java.net/samples.html and https://computefarm.dev.java.net/source/browse/computefarm/trunk/samples/src/java/org/tiling/computefarm/samples/junit/.
I think this would be a nice general application of Hadoop, and we'd be able to avoid the restriction on tests having to be Serializable.
However, for the immediate problem of reducing test execution time on Hudson, Doug's suggestion of writing a custom ant task sounds like it would be more appropriate.
> a distributed junit test runner
> -------------------------------
>
> Key: HADOOP-1257
> URL: https://issues.apache.org/jira/browse/HADOOP-1257
> Project: Hadoop
> Issue Type: New Feature
> Components: test
> Affects Versions: 0.12.3
> Reporter: Owen O'Malley
> Assigned To: Owen O'Malley
>
> It would be nice to have a distributed junit runner that would run 100 instances of each test a separate map, and use counters to count how many times each test passed/failed/hung.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.