Hi Travis, That seems a little long considering the number of failures.
Final results , PASSED: 107 FAILED: 8 SKIPPED: 0 ABORTED: 3 FAILED DEPENDENCY: 3 Total time: 64 minutes 55 seconds These are the test results run against Hadoop23. Normally there are 7 failures, 3 aborts, 0 failed dependencies. The failures come from broken negative tests. The three aborts are from broken hbase tests. The additional failure here is a known issue with the latest version of Hadoop23 and causes the 3 failed dependencies. You should not see this if you are building and testing against Hadoop20. Hope this helps. chris On 10/20/12 1:02 PM, "Travis Crawford (JIRA)" <[email protected]> wrote: > > [ >https://issues.apache.org/jira/browse/HCATALOG-535?page=com.atlassian.jira >.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13480822#c >omment-13480822 ] > >Travis Crawford commented on HCATALOG-535: >------------------------------------------ > >Without much tinkering most of the tests pass, and took ~90 minutes. >Question for someone who's run these before - how long do they typically >take? > >{code} >[exec] Final results , PASSED: 96 FAILED: 21 SKIPPED: 0 ABORTED: 4 FAILED >DEPENDENCY: 0 >Total time: 91 minutes 30 seconds >{code} > >Hopefully the ones that have failed are due to some common reason. Will >check the logs out to see what's up. > >> HCatalog e2e tests should run locally with minimal configuration >> ---------------------------------------------------------------- >> >> Key: HCATALOG-535 >> URL: https://issues.apache.org/jira/browse/HCATALOG-535 >> Project: HCatalog >> Issue Type: Improvement >> Reporter: Travis Crawford >> Assignee: Travis Crawford >> >> Setting up the environment to run e2e tests is documented here: >> https://cwiki.apache.org/confluence/display/HCATALOG/How+To+Test >> Its extremely time consuming to setup because there are so many moving >>parts. Some are very machine-specific, like configuring SSH and >>installing MySQL for your platform. However, some stuff we can automate >>for the developer, like downloading, installing & configuring all the >>Java stuff. We should do that to simplify. >> Also, tests do not run from a git repo because of the svn external. >>This would be very helpful to fix. Developing with Git is WAAAAAY nicer >>because branching is so easy. > >-- >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
