[
https://issues.apache.org/jira/browse/HADOOP-7019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973331#action_12973331
]
Konstantin Boudnik commented on HADOOP-7019:
--------------------------------------------
I'll try to explain it once more:
bq. But the fi tests are already covered by 'test' and 'test-patch', so your
fear is unfounded.
FI tests aren't covered by {{test-patch}}. System tests are. They _are_
different.
bq. When running a single test (~1s), leaving the fi targets increase the total
time 3x+ to 71 seconds
Sorry, where the multiplier comes from? Does it indicates the number of
subprojects?
bq. ant test-core -Dtestcase=TestUserGroupInformation
ant run-test-core... will produce desired result. That's why FI tests were
never included into {{run-test-core}} target.
Again, this is the matter of opinion. Current target's hierarchy was discussed
at the time when fault injection framework has been introduced into Hadoop
source code base. If the community decides that FI tests shouldn't executed as
a part of core test-cycle - so be it. And then this issues needs to be
separated (according to your own logic from a upstream JIRA) into two JIRAs:
one for system test artifacts and another one for FI tests.
> Refactor build targets to enable faster cross project dev cycles.
> -----------------------------------------------------------------
>
> Key: HADOOP-7019
> URL: https://issues.apache.org/jira/browse/HADOOP-7019
> Project: Hadoop Common
> Issue Type: Bug
> Components: build
> Reporter: Owen O'Malley
> Assignee: Luke Lu
> Fix For: 0.22.0
>
> Attachments: hadoop-7019-trunk-v1.patch
>
>
> The current build always generates fault injection artifacts and pushes them
> to Maven. Most developers have no need for these artifacts and no users need
> them.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
