[
https://issues.apache.org/jira/browse/HBASE-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13175718#comment-13175718
]
nkeywal commented on HBASE-5064:
--------------------------------
Below a review of the tests on trunk & prebuild.
We have often, nearly always, hanging tests in hadoop-qa, while it's occurs
only sometimes on main build.
It seems that it hangs more often when // is activated
It seems that we have this kind of behavior when we cannot start a thread.
I will look if we can enhance the reporting in surefire (i.e. it seems some
errors are not reported today)
----
#2572
Tests run: 789, Failures: 0, Errors: 0, Skipped: 9
#2570
Tests run: 789, Failures: 0, Errors: 0, Skipped: 9
#2569
Tests run: 789, Failures: 0, Errors: 0, Skipped: 9
#2568
Tests run: 789, Failures: 0, Errors: 0, Skipped: 9
#2566
Tests run: 789, Failures: 0, Errors: 0, Skipped: 9
#2565 (marked as success, but there is a hanging test)
wal.TestLogRollAbort
#596 5064 1 processesn min number of threads
Tests run: 786, Failures: 3, Errors: 1, Skipped: 9
#595 5064.v7.patch - 3 processesn min number of threads
Tests run: 785, Failures: 3, Errors: 1, Skipped: 9
hbck.TestOfflineMetaRebuildOverlap
master.TestMasterRestartAfterDisablingTable
replication.TestMasterReplication
#594 5064.v7.patch - 3 processesn min number of threads
Tests run: 786, Failures: 3, Errors: 1, Skipped: 9
util.TestMiniClusterLoadParallel
coprocessor.TestMasterCoprocessorExceptionWithRemove
#593
Tests run: 779, Failures: 4, Errors: 2, Skipped: 9
util.TestMiniClusterLoadSequential
#592 - Data-block-encoding-2011-12-23.patch - fails, but with a clear message
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (malloc) failed to allocate 32756 bytes for
ChunkPool::allocate
# An error report file with more information is saved as:
#
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/trunk/hs_err_pid20773.log
Tests run: 739, Failures: 3, Errors: 1, Skipped: 9
#591 - scannerMVCC1.txt
Tests run: 780, Failures: 3, Errors: 1, Skipped: 9
master.TestDistributedLogSplitting
#589 - 5064.v12.patch, 2 threads
Tests run: 783, Failures: 3, Errors: 1, Skipped: 9
coprocessor.TestMasterCoprocessorExceptionWithRemove
hbase.TestRegionRebalancing
master.TestDistributedLogSplitting
#588 - 5064 4 threads
Tests run: 768, Failures: 3, Errors: 1, Skipped: 9
util.hbck.TestOfflineMetaRebuildBase
catalog.TestMetaReaderEditor
coprocessor.TestMasterCoprocessorExceptionWithRemove
replication.regionserver.TestReplicationSink
replication.TestMasterReplication
#587 - 5064 (7 processes, standard config)
replication.TestMasterReplication
master.TestMasterFailover
master.TestRollingRestart
#586 - 5064 (6 processes, min number of threads)
Tests run: 775, Failures: 3, Errors: 1, Skipped: 9
master.TestRestartCluster
regionserver.wal.TestLogRollAbort
client.TestMetaScanner
TestGlobalMemStoreSize
client.TestMultiParallel
#585 - 5064 (3 processes, min number of threads)
Tests run: 788, Failures: 4, Errors: 1, Skipped: 9
#583 - HBASE-4720.trunk.v2.patch
Tests run: 788, Failures: 3, Errors: 1, Skipped: 9
replication.TestMasterReplication
#582 - Delta-encoding.patch-2011-12-22_11_52_07.patch
unable to create new native thread
replication.TestReplication:
Tests run: 2, Failures: 0, Errors: 1, Skipped: 0
> 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.v10.patch, 5064.v11.patch,
> 5064.v12.patch, 5064.v2.patch, 5064.v3.patch, 5064.v4.patch, 5064.v5.patch,
> 5064.v6.patch, 5064.v6.patch, 5064.v6.patch, 5064.v6.patch, 5064.v7.patch,
> 5064.v7.patch, 5064.v7.patch, 5064.v7.patch, 5064.v7.patch, 5064.v8.patch,
> 5064.v8.patch, 5064.v9.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
