hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-6172) TestDbClasses timeouts are too aggressive
Date Tue, 02 Dec 2014 11:43:16 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-6172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231366#comment-14231366
] 

Hudson commented on MAPREDUCE-6172:
-----------------------------------

ABORTED: Integrated in Hadoop-Hdfs-trunk #1951 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1951/])
MAPREDUCE-6172. TestDbClasses timeouts are too aggressive. Contributed by Varun Saxena (jlowe:
rev 2b30fb1053e70c128b98013fb63cf9a095623be6)
* hadoop-mapreduce-project/CHANGES.txt
* hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/test/java/org/apache/hadoop/mapreduce/lib/db/TestDbClasses.java


> 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)

Mime
View raw message