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/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] Updated: (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 updated HADOOP-6810:
---------------------------------------
Attachment: smoke-tests.patch
Addressing Jacob's comment: {{core-test}} behavior is unchanged in this version. However, the overlap of running {{test-smoke}} followed by {{core-test}} will be equal to that of {{test-smoke}} tests.
> 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.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.
[jira] Commented: (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:comment-tabpanel&focusedCommentId=12877175#action_12877175 ]
Konstantin Boudnik commented on HADOOP-6810:
--------------------------------------------
Have spoken with Boris offline and he expresses the concern that excluding commit and smoke tests from {{test-core}} target. While this is a valid concern because the set of core tests is changing by the patch without it {{test-core}} execution will increase by about 40 minutes (13 minutes from commit tests, which we already have in place, and about 30 minutes from smokes).
Any thoughts?
> 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
> Attachments: 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.
[jira] Commented: (HADOOP-6810) Extract a subset of tests for smoke
(DOA) validation
Posted by "Jakob Homan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877246#action_12877246 ]
Jakob Homan commented on HADOOP-6810:
-------------------------------------
I tend to agree with Boris. With the current patch, if I run test-core, the behavior changes so that those tests in commit and smoke will *not* be run, correct? That would be a big change from what users have grown used to. I had assumed that commit tests are a subset of smoke tests are a subset of core-tests are a subset of test. I had made previous comments that if you run, say ant commit-tests test, you would end up running the members of commit-tests twice, which was suboptimal. But I'm not sure the other side of that - three separate disjoint sets - is also optimal.
Except for this behavior change, the patch looks good.
> 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.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.
[jira] Updated: (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 updated HADOOP-6810:
---------------------------------------
Attachment: (was: smoke-tests.1)
> 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.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.
[jira] Updated: (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 updated HADOOP-6810:
---------------------------------------
Attachment: smoke-tests.patch
Now the list of smoke tests is formed pretty much to its final shape. Ready for a review, I suppose.
> 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
> Attachments: 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.
[jira] Commented: (HADOOP-6810) Extract a subset of tests for smoke
(DOA) validation
Posted by "Jakob Homan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884046#action_12884046 ]
Jakob Homan commented on HADOOP-6810:
-------------------------------------
Updated patch-on-the-patch looks good. Thanks. +1 for 20S.
> 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.
[jira] Commented: (HADOOP-6810) Extract a subset of tests for smoke
(DOA) validation
Posted by "Jakob Homan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877263#action_12877263 ]
Jakob Homan commented on HADOOP-6810:
-------------------------------------
+1 for Y20.
> 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.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.
[jira] Updated: (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 updated HADOOP-6810:
---------------------------------------
Attachment: smoke-tests.patch
Initial patch with preliminary list of tests for MR. Core/HDFS test list to be added.
> 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
> Attachments: 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.
[jira] Updated: (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 updated HADOOP-6810:
---------------------------------------
Attachment: smoke-tests.1.patch
Addressing Jacob offline comment about name of a variable. This patch should go on top of {{smoke-test.patch}}
> 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.
[jira] Updated: (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 updated HADOOP-6810:
---------------------------------------
Attachment: (was: smoke-tests.patch.1)
> 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.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.
[jira] Commented: (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:comment-tabpanel&focusedCommentId=12875815#action_12875815 ]
Konstantin Boudnik commented on HADOOP-6810:
--------------------------------------------
To be clean, the above patch is for 0.20.3 branch.
> 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
> Attachments: 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.
[jira] Updated: (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 updated HADOOP-6810:
---------------------------------------
Attachment: smoke-tests.patch.1
This patch goes on top of the previous one in order to have a separate target which runs test-core test set excluding that of commit and smoke tests. {{test-core}} behavior left intact and new target is added for the purpose of eliminating test run dups.
A separate combined patch for HDFS/MR trunks is coming
> 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.patch, smoke-tests.patch, smoke-tests.patch, smoke-tests.patch, smoke-tests.patch, smoke-tests.patch.1
>
>
> 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] Updated: (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 updated HADOOP-6810:
---------------------------------------
Assignee: Konstantin Boudnik
Affects Version/s: 0.21.0
(was: 0.20.3)
I think I have made it all confusing by setting 0.20 as the target. The attached patch is for internal Yahoo 20 release and trunk patch will be add here shortly. Trunk versions for HDFS/MR will follow shortly as well.
> 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.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.
[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.
[jira] Updated: (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 updated HADOOP-6810:
---------------------------------------
Attachment: smoke-tests.1
This patch addresses the issue with test duplication entries. Please review.
> 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, smoke-tests.patch, smoke-tests.patch, smoke-tests.patch, smoke-tests.patch, smoke-tests.patch, smoke-tests.patch.1
>
>
> 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] Commented: (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:comment-tabpanel&focusedCommentId=12875807#action_12875807 ]
Konstantin Boudnik commented on HADOOP-6810:
--------------------------------------------
It is different for 0.20 branch where all tests are mixed together.
For HDFS/MR we'll need a separate JIRAs.
> 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] Commented: (HADOOP-6810) Extract a subset of tests for smoke
(DOA) validation
Posted by "Jakob Homan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12875797#action_12875797 ]
Jakob Homan commented on HADOOP-6810:
-------------------------------------
How would this be different than the current commit (run-commit-test) test suite? That suite may need to be updated, it's been a while. The Common tests already take less than 10 minutes to run...
> 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] Updated: (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 updated HADOOP-6810:
---------------------------------------
Attachment: smoke-tests.patch
This version of the patch excludes commit and smoke tests from {{test-core}} to eliminate the duplication. Instead {{test-commit}} and {{test-smoke}} are included to the {{test}} along with {{test-core}}
This patch is for 0.20.3. As 0.20.3 release might not happen I am including this patch in case someone needs it eventually.
> 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
> Attachments: 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.
[jira] Commented: (HADOOP-6810) Extract a subset of tests for smoke
(DOA) validation
Posted by "Jakob Homan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877649#action_12877649 ]
Jakob Homan commented on HADOOP-6810:
-------------------------------------
Updated patch looks good. I notice line 12 is indented a couple characters too far. I also just noticed that the smoke test list contains duplicates of from the commit list, meaning those tests will be run twice even with this change.
> 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.patch, smoke-tests.patch, smoke-tests.patch, smoke-tests.patch, smoke-tests.patch, smoke-tests.patch.1
>
>
> 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] Updated: (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 updated HADOOP-6810:
---------------------------------------
Attachment: smoke-tests.patch
Adding comments to the test list to separate test specific to common from hdfs
> 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
> Attachments: 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.