hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Badger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-7040) TestConfigurationNodeLabelsProvider.testConfigTimer
Date Thu, 17 Aug 2017 15:00:02 GMT

    [ https://issues.apache.org/jira/browse/YARN-7040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16130520#comment-16130520

Eric Badger commented on YARN-7040:

Looks like a race condition in the test. The test sets a timer with an interval of 1000ms
and sleeps for 1500ms assuming that the timer will fire during that time period. If the timer
thread runs slowly then the node label won't get updated by the time that it is checked in
the test. The timer thread needs to run pretty slowly (500 ms slower than the test code thread),
but I've seen it happen twice now.

> TestConfigurationNodeLabelsProvider.testConfigTimer
> ---------------------------------------------------
>                 Key: YARN-7040
>                 URL: https://issues.apache.org/jira/browse/YARN-7040
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Eric Badger
> {noformat}
> java.lang.AssertionError: expected:<[<X:exclusivity=true>]> but was:<[<A:exclusivity=true>]>
> 	at org.junit.Assert.fail(Assert.java:88)
> 	at org.junit.Assert.failNotEquals(Assert.java:743)
> 	at org.junit.Assert.assertEquals(Assert.java:118)
> 	at org.junit.Assert.assertEquals(Assert.java:144)
> 	at org.apache.hadoop.yarn.nodelabels.NodeLabelTestBase.assertNLCollectionEquals(NodeLabelTestBase.java:117)
> 	at org.apache.hadoop.yarn.server.nodemanager.nodelabels.TestConfigurationNodeLabelsProvider.testConfigTimer(TestConfigurationNodeLabelsProvider.java:144)
> {noformat}

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message