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

Brock Noland commented on HIVE-4675:
------------------------------------

To summarize, here is where we are at:

-HIVE-4675 (this jira) contains ptest2 which works on a fixed number of 
dedicated hosts
-HIVE-4815 updates ptest2 to work with ec2 spot instances
-An Apache Jenkins build has been executing over the holiday weekend 

What are you thoughts on committing HIVE-4675 and HIVE-4815 [~ashutoshc]?

I have been using ptest2 to execute Hive trunk builds on the Apache jenkins: 
https://builds.apache.org/job/Hive-trunk-hadoop1-ptest/. The tests have been 
running on ec2 spot instances. Things have been going very well. It takes about 
2 hours via 8 XL ec2 spot instances. Since build 27 I have only been making 
minor changes.

Summary of Builds since stabilization
* Passed [28, 29, 33, 34, 35, 36, 38, 39, 40]
* Failed due a flaky test [27, 30, 37]
* Failed due to my mistake [31, 32] (compilation error) [41] (restarted the 
webserver hosting the service)
                
> Create new parallel unit test environment
> -----------------------------------------
>
>                 Key: HIVE-4675
>                 URL: https://issues.apache.org/jira/browse/HIVE-4675
>             Project: Hive
>          Issue Type: Improvement
>          Components: Testing Infrastructure
>            Reporter: Brock Noland
>            Assignee: Brock Noland
>             Fix For: 0.12.0
>
>         Attachments: HIVE-4675.patch
>
>
> The current ptest tool is great, but it has the following limitations:
> -Requires an NFS filer
> -Unless the NFS filer is dedicated ptests can become IO bound easily
> -Investigating of failures is troublesome because the source directory for 
> the failure is not saved
> -Ignoring or isolated tests is not supported
> -No unit tests for the ptest framework exist
> It'd be great to have a ptest tool that addresses this limitations.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to