[
https://issues.apache.org/jira/browse/MAPREDUCE-6172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14227246#comment-14227246
]
Hadoop QA commented on MAPREDUCE-6172:
--------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12683992/MAPREDUCE-6172.patch
against trunk revision c1f2bb2.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5052//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5052//console
This message is automatically generated.
> TestDbClasses timeouts are too aggressive
> -----------------------------------------
>
> Key: MAPREDUCE-6172
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6172
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: test
> Affects Versions: 2.6.0
> Reporter: Jason Lowe
> Assignee: Varun Saxena
> Priority: Minor
> Fix For: 2.7.0
>
> Attachments: MAPREDUCE-6172.patch
>
>
> Some of the TestDbClasses test timeouts are only 1 second, and some of those
> tests perform disk I/O which could easily exceed the test timeout if the disk
> is busy or there's some other hiccup on the system at the time. We should
> increase these timeouts to something more reasonable (i.e.: 10 or 20 seconds).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
