[
https://issues.apache.org/jira/browse/MAPREDUCE-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15286870#comment-15286870
]
Hudson commented on MAPREDUCE-6698:
-----------------------------------
ABORTED: Integrated in Hadoop-trunk-Commit #9793 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/9793/])
MAPREDUCE-6698. Increase timeout on (jlowe: rev
34fddd1e912dcd9f898e500b8df11295ee49c0d8)
*
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs/src/test/java/org/apache/hadoop/mapreduce/v2/hs/TestUnnecessaryBlockingOnHistoryFileInfo.java
> Increase timeout on
> TestUnnecessaryBlockingOnHistoryFileInfo.testTwoThreadsQueryingDifferentJobOfSameUser
> ---------------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-6698
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6698
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobhistoryserver
> Affects Versions: 2.8.0
> Reporter: Haibo Chen
> Assignee: Haibo Chen
> Fix For: 2.8.0
>
> Attachments: mapreduce6698.001.patch
>
>
> The timeout on
> TestUnnecessaryBlockingOnHistoryFileInfo.testTwoThreadsQueryingDifferentJobOfSameUser
> is added to verify the fix of MAPREDUCE-6684 works. When two thread are
> requesting different jobs owned by the same user, one thread request jobA
> should not be blocked by the other that is processing a large job jobB. The
> timeout exception, if happened, should ideally indicate the fix does not
> work. But the timeout period is set too aggressive, so the test always fails
> on slow VMs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
