[ 
https://issues.apache.org/jira/browse/HADOOP-7019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973309#action_12973309
 ] 

Luke Lu commented on HADOOP-7019:
---------------------------------

I appreciate your concern, cos. But the fi tests are already covered by 'test' 
and 'test-patch', so your fear is unfounded.

bq. Thus removing the target from test-core cycle solves nothing. 

It solves a couple of things:

* Decouple  fi tests from core tests so they can be developed separately in 
parallel by different group of people. Many devs except some hdfs folks working 
on a specific set of problems don't care about fi tests in there dev cycles. It 
enables fast API change dev cycles across projects, which otherwise would be 
hampered by non-compiling fi code because the way aop works (brittle to API 
changes.)
* When running a *single* test (~1s), leaving the fi targets increase the total 
time 3x+ to 71 seconds, from which "weaving aspects" takes about a minute.
** Before my changes: ant test-core -Dtestcase=TestUserGroupInformation takes 
71 seconds in repeated runs with no change to source code. The test itself 
takes less than a second. 
** After my changes the same test takes 20 seconds (our build overhead is huge! 
which can be improved, which will lead to even dramatic speed up, as the aspect 
weaving time is O(n) to the code base, i.e., it'll getting slower), 15s if we 
remove the paranamer (from avro) process.

> 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.

Reply via email to