hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "nkeywal (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-5064) use surefire tests parallelization
Date Mon, 19 Dec 2011 08:24:30 GMT

    [ https://issues.apache.org/jira/browse/HBASE-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13172086#comment-13172086

nkeywal commented on HBASE-5064:

Tests run: 780, Failures: 4, Errors: 2, Skipped: 9
Total time: 1:05:24.474s

To be compared with prebuild #535:
Tests run: 785, Failures: 0, Errors: 3, Skipped: 9
Total time: 1:49:04.397s

Still faster (~45minutes)
Still some tests missing in the final report: (795 vs. 797). Don't know why yet.

TestInstantSchemaChange.testInstantSchemaJanitor: Too many open files
TestFromClientSide.testPoolBehavior: Fixed in v4.
TestTableMapReduce.testMultiRegionTable: NumberFormatException
TestHFileOutputFormat.testMRIncrementalLoad: NumberFormatException
TestHFileOutputFormat.testMRIncrementalLoadWithSplit: NumberFormatException
TestHFileOutputFormat.testExcludeMinorCompaction: NumberFormatException

NumberFormatException: seems to be unrelated, I've got it on other patches as well.

@stack: it's a parallelisation per process, so it should not be necessary: there is no added
load on maven itself. However, the results of the first run seem to say that the hadoop-qa
machine was overloaded. But it seems that the other runs went well.

> use surefire tests parallelization
> ----------------------------------
>                 Key: HBASE-5064
>                 URL: https://issues.apache.org/jira/browse/HBASE-5064
>             Project: HBase
>          Issue Type: Improvement
>          Components: test
>    Affects Versions: 0.94.0
>            Reporter: nkeywal
>            Assignee: nkeywal
>            Priority: Minor
>         Attachments: 5064.patch, 5064.patch, 5064.v2.patch, 5064.v3.patch, 5064.v4.patch
> To be tried multiple times on hadoop-qa before committing.

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


View raw message