[
https://issues.apache.org/jira/browse/MAPREDUCE-5631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13826611#comment-13826611
]
Jason Lowe commented on MAPREDUCE-5631:
---------------------------------------
Could you elaborate on how the configuration is leaking between tests? The
test cases all construct a new Configuration object and call setConf with it,
so I'm not seeing how the configuration setting from one test is leaking into
another. Seems more likely the properties being explicitly set by the patch
were being accidentally picked up from a mapred-site.xml file in some
environments which would break the test. Just want to make sure I understand
the nature of the fix.
Minor nit in the patch: the order of the last two arguments in the following
code should be flipped since the Assert.assertEquals calling convention is
{{expected, actual}} instead of {{actual, expected}}:
{code}
Assert.assertEquals("Only 1 try was expected but was : "
+ this.notificationCount, this.notificationCount, 1);
{code}
> TestJobEndNotifier.testNotifyRetries fails with Should have taken more than 5
> seconds in jdk7
> ---------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-5631
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5631
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 3.0.0, 2.3.0, 0.23.10
> Reporter: Jonathan Eagles
> Assignee: Jonathan Eagles
> Labels: java7
> Attachments: MAPREDUCE-5631.patch
>
>
> Configuration settings are bleeding over from test to test in jdk7
> environment since tests are run in random order.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
