[ 
https://issues.apache.org/jira/browse/WHIRR-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12989640#comment-12989640
 ] 

Tibor Kiss edited comment on WHIRR-55 at 2/2/11 2:17 PM:
---------------------------------------------------------

Thx.
Last time I have made successful integration tests when I applied my WHIRR-167 
patch to the 1059503 revision on the trunk.
Now we are at 1065812 revision on the trunk. Somewhere in between these 
revision numbers has been introduced the problem. I'm sure you or somebody else 
can further reduce the interval of search.

Even if you have CI server, sometimes is inefficient to run integration tests 
on each patch you apply. Maybe a few patches together it worst, then if fails 
further dividing can be applied. The problem to automate the integration test 
while merging the patches is caused by the fact that sometimes you want to run 
the integration test before you are commiting. I don't know how this can be 
solved, or you just commit merge the patches into trunk, then one by one you 
will wait for the results on CI server? (sorry for offtopic).

      was (Author: tibor.kiss):
    Thx.
Last time I have made successful integration tests it was when I applied my 
WHIRR-167 patch to the 1059503 revision on the trunk.
Now it we are at 1065812 revision on the trunk. Somewhere in between these 
revision numbers has been introduced the problem. I'm sure you or somebody else 
can further reduce the interval of search.

Even if you have CI server, sometimes is inefficient to run integration tests 
on each patch you apply. Maybe a few patches together it worst, then if fails 
further dividing can be applied. The problem to automate the integration test 
while merging the patches is caused by the fact that sometimes you want to run 
the integration test before you are commiting. I don't know how this can be 
solved, or you just commit merge the patches into trunk, then one by one you 
will wait for the results on CI server? (sorry for offtopic).
  
> Users should be able to override an arbitrary Hadoop property before launch
> ---------------------------------------------------------------------------
>
>                 Key: WHIRR-55
>                 URL: https://issues.apache.org/jira/browse/WHIRR-55
>             Project: Whirr
>          Issue Type: Improvement
>          Components: service/hadoop
>            Reporter: Tom White
>            Assignee: Tom White
>             Fix For: 0.4.0
>
>         Attachments: WHIRR-55.patch, WHIRR-55.patch, WHIRR-55.patch, 
> WHIRR-55.patch
>
>


-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to