[
https://issues.apache.org/jira/browse/MAPREDUCE-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726883#action_12726883
]
Sreekanth Ramakrishnan commented on MAPREDUCE-522:
--------------------------------------------------
output from ant test-patch:
{noformat}
[exec]
[exec] +1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] +1 tests included. The patch appears to include 12 new or
modified tests.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning
messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number
of javac compiler warnings.
[exec]
[exec] +1 findbugs. The patch does not introduce any new Findbugs
warnings.
[exec]
[exec] +1 release audit. The applied patch does not increase the
total number of release audit warnings.
[exec]
[exec]
{noformat}
> Rewrite TestQueueCapacities to make it simpler and avoid timeout errors
> -----------------------------------------------------------------------
>
> Key: MAPREDUCE-522
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-522
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Hemanth Yamijala
> Attachments: mapred-522-ydist.patch, mapreduce-522-2.patch,
> mapreduce-522-3.patch, mapreduce-522-4.patch
>
>
> We have seen TestQueueCapacities fail periodically and there have been a
> couple of times fixes partially fixed the problem, the most recent instance
> being HADOOP-5869. I found another instance of failure, while running tests
> locally while testing a different patch. This was a different symptom from
> the ones we've seen before. The core problem is that the test is too complex
> and relies on too many things working correctly to be useful. It would make
> sense to revisit the purpose of the test and see if a simpler model can serve
> it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
