[
https://issues.apache.org/jira/browse/HBASE-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13176814#comment-13176814
]
Zhihong Yu commented on HBASE-5064:
-----------------------------------
Test failure isn't always associated with NumberFormatException.
I ran tests with patch 15 and saw the following in TestTableMapReduce-output:
{code}
2011-12-28 09:28:40,839 DEBUG [pool-1-thread-1]
client.HConnectionManager$HConnectionImplementation(1228): Cached location for
mrtest,rrr,1325093287841.463ef8c4d900c4b3c9f1d2df476e1bd9. is sea-lab-1:36329
2011-12-28 09:28:40,840 DEBUG [pool-1-thread-1]
client.HConnectionManager$HConnectionImplementation(1228): Cached location for
mrtest,sss,1325093287841.d4448f0cc9806499135566cb47630427. is sea-lab-1:36329
2011-12-28 09:28:40,840 DEBUG [pool-1-thread-1]
client.HConnectionManager$HConnectionImplementation(1228): Cached location for
mrtest,ttt,1325093287841.1ca6fb61e8ce69ce8505cfd7b157008c. is sea-lab-1:36329
2011-12-28 09:28:40,840 DEBUG [pool-1-thread-1]
client.HConnectionManager$HConnectionImplementation(1228): Cached location for
mrtest,uuu,1325093287841.b74b52fb22bea8b1fd100e225943ab58. is sea-lab-1:36329
2011-12-28 09:28:40,841 DEBUG [pool-1-thread-1]
client.HConnectionManager$HConnectionImplementation(1228): Cached location for
mrtest,vvv,1325093287841.f50b26a0272f89c2123d80b8d13592b8. is sea-lab-1:36329
2011-12-28 09:28:40,841 INFO [pool-1-thread-1]
mapred.TableInputFormatBase(142): split: 1->sea-lab-1:mmm,
2011-12-28 09:28:41,948 DEBUG [Finalizer]
client.HConnectionManager$HConnectionImplementation(1859): The connection to
null was closed by the finalize method.
2011-12-28 09:28:56,283 WARN [JVM Runner
jvm_20111228092823016_0001_m_1001648490 spawned.]
mapred.DefaultTaskController(137): Exit code from task is : 1
2011-12-28 09:28:56,284 WARN [Thread-368] mapred.TaskRunner(270):
attempt_20111228092823016_0001_m_000000_0 : Child Error
java.io.IOException: Task process exit with nonzero status of 1.
at org.apache.hadoop.mapred.TaskRunner.run(TaskRunner.java:258)
2011-12-28 09:29:03,464 WARN [JVM Runner
jvm_20111228092823016_0001_m_1912611626 spawned.]
mapred.DefaultTaskController(137): Exit code from task is : 1
2011-12-28 09:29:03,465 WARN [Thread-390] mapred.TaskRunner(270):
attempt_20111228092823016_0001_m_000000_0 : Child Error
java.io.IOException: Task process exit with nonzero status of 1.
at org.apache.hadoop.mapred.TaskRunner.run(TaskRunner.java:258)
java.lang.Throwable: Child Error
at org.apache.hadoop.mapred.TaskRunner.run(TaskRunner.java:271)
Caused by: java.io.IOException: Task process exit with nonzero status of 1.
at org.apache.hadoop.mapred.TaskRunner.run(TaskRunner.java:258)
java.lang.Throwable: Child Error
at org.apache.hadoop.mapred.TaskRunner.run(TaskRunner.java:271)
Caused by: java.io.IOException: Task process exit with nonzero status of 1.
at org.apache.hadoop.mapred.TaskRunner.run(TaskRunner.java:258)
2011-12-28 09:29:10,565 WARN [1318497351@qtp-99120402-1]
mapred.TaskLogServlet(111): Failed to retrieve stdout log for task:
attempt_20111228092823016_0001_m_000000_0
java.io.FileNotFoundException:
/home/hduser/trunk/../logs/userlogs/job_20111228092823016_0001/attempt_20111228092823016_0001_m_000000_0/log.index
(No such file or directory)
{code}
> 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.v13.patch, 5064.v14.patch, 5064.v14.patch,
> 5064.v15.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