[
https://issues.apache.org/jira/browse/HDFS-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732823#action_12732823
]
Jakob Homan commented on HDFS-458:
----------------------------------
I considered that but thought that having one easy-to-edit source of tests
would be a benefit. Add a test? Add its name. Delete a delete? Delete it. I
think a plain text file is good for this type of info. Further, having them run
in the same configuration as they would normally be run through ant via the
update build file is nice as well.
That being said, once the tagging/test categorization setup is complete, I
definitely want to move to using that. I'd much rather be able to prefer to be
able to annotate specific tests within each test suite to be included in the
10-minute set. Right now we have to have all the tests from each suite
included, rather than on a test-by-test basis. As soon as that's up and
running, we should convert over.
> Create target for 10 minute patch test build for hdfs
> -----------------------------------------------------
>
> Key: HDFS-458
> URL: https://issues.apache.org/jira/browse/HDFS-458
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: test
> Reporter: Jakob Homan
> Assignee: Jakob Homan
> Attachments: build.xml, HDFS-458.patch, HDFS-458.patch,
> TenMinuteTestData.xlsx
>
>
> It would be good to identify a subset of hdfs tests that provide strong test
> code coverage within 10 minutes, as is the goal of MAPREDUCE-670 and
> HADOOP-5628.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
