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 "Konstantin Boudnik (JIRA)" <ji...@apache.org> on 2010/06/05 01:46:03 UTC
[jira] Created: (HADOOP-6810) Extract a subset of tests for smoke
(DOA) validation
Extract a subset of tests for smoke (DOA) validation
----------------------------------------------------
Key: HADOOP-6810
URL: https://issues.apache.org/jira/browse/HADOOP-6810
Project: Hadoop Common
Issue Type: Improvement
Components: test
Affects Versions: 0.20.3
Reporter: Konstantin Boudnik
Currently, there's no way to quickly find out if a new build of Hadoop is reasonably viable and can be used for future development/testing cycle.
Similarly to 'commit' testing it'd be great to have a wider subset of existing tests to be executed inside of 30 minutes. The main goal of such a subset is to have a reasonable guarantees that different parts of Hadoop's functionality aren't broken and the system is not DOA.
Full test run takes about 3+ hours and it is a too long wait time in many cases.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HADOOP-6810) Extract a subset of tests for smoke
(DOA) validation
Posted by "Konstantin Boudnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantin Boudnik resolved HADOOP-6810.
----------------------------------------
Resolution: Later
I'd like to close it for now as 'Later' until Common has enough tests to separate a smoke suite. Right not it doesn't make much sense.
> Extract a subset of tests for smoke (DOA) validation
> ----------------------------------------------------
>
> Key: HADOOP-6810
> URL: https://issues.apache.org/jira/browse/HADOOP-6810
> Project: Hadoop Common
> Issue Type: Improvement
> Components: test
> Affects Versions: 0.21.0
> Reporter: Konstantin Boudnik
> Assignee: Konstantin Boudnik
> Attachments: smoke-tests.1.patch, smoke-tests.patch, smoke-tests.patch, smoke-tests.patch, smoke-tests.patch, smoke-tests.patch
>
>
> Currently, there's no way to quickly find out if a new build of Hadoop is reasonably viable and can be used for future development/testing cycle.
> Similarly to 'commit' testing it'd be great to have a wider subset of existing tests to be executed inside of 30 minutes. The main goal of such a subset is to have a reasonable guarantees that different parts of Hadoop's functionality aren't broken and the system is not DOA.
> Full test run takes about 3+ hours and it is a too long wait time in many cases.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.