[
https://issues.apache.org/jira/browse/HBASE-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257916#comment-13257916
]
Jonathan Hsieh commented on HBASE-5831:
---------------------------------------
I tried the tested in question on trunk and it passes in eclipse. It fails in
mvn. I've encountered this kind of problem previously as well with HBASE-5793
-- my eclipse setup differs from mvn by not using
./src/test/resources/hbase-site.xml in the resources dir.
Since the test expects and error, my guess is this may have to do with the
client retry number getting bumped up to 100 in the resource hbase-site.xml
file in HBASE-5747.
When I edited that file back down client retries to 10 it passes in about 2
minutes.
> hadoopqa builds not completing
> ------------------------------
>
> Key: HBASE-5831
> URL: https://issues.apache.org/jira/browse/HBASE-5831
> Project: HBase
> Issue Type: Bug
> Components: test
> Reporter: stack
> Assignee: stack
> Priority: Blocker
> Attachments: 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt,
> 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt,
> 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt,
> 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt,
> 5831.remove.TestLoadIncrementalHFilesSplitRecovery.txt,
> 5831.remove.all.mapreduce.txt
>
>
> No test failures but build complains it has failed. trunk build seems to
> have the same affliction:
> {code}
> Results :
> Tests run: 909, Failures: 0, Errors: 0, Skipped: 9
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 41:19.273s
> [INFO] Finished at: Wed Apr 18 21:54:31 UTC 2012
> [INFO] Final Memory: 59M/451M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.12-TRUNK-HBASE-2:test
> (secondPartTestsExecution) on project hbase: Failure or timeout -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> -1 overall. Here are the results of testing the latest attachment
> http://issues.apache.org/jira/secure/attachment/12523250/5811+%281%29.txt
> against trunk revision .
> +1 @author. The patch does not contain any @author tags.
> +1 tests included. The patch appears to include 3 new or modified tests.
> +1 javadoc. The javadoc tool did not generate any warning messages.
> +1 javac. The applied patch does not increase the total number of javac
> compiler warnings.
> -1 findbugs. The patch appears to introduce 6 new Findbugs (version
> 1.3.9) warnings.
> +1 release audit. The applied patch does not increase the total number
> of release audit warnings.
> -1 core tests. The patch failed these unit tests:
> {code}
> Its not apparent that any particular test is not finishing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
