You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Tsz Wo Nicholas Sze (JIRA)" <ji...@apache.org> on 2014/04/08 23:45:18 UTC
[jira] [Commented] (HADOOP-10473) TestCallQueueManager is still
flaky
[ https://issues.apache.org/jira/browse/HADOOP-10473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13963481#comment-13963481 ]
Tsz Wo Nicholas Sze commented on HADOOP-10473:
----------------------------------------------
The test may fail as shown below.
{noformat}
java.lang.AssertionError: expected:<42264> but was:<42284>
at org.junit.Assert.fail(Assert.java:93)
at org.junit.Assert.failNotEquals(Assert.java:647)
at org.junit.Assert.assertEquals(Assert.java:128)
at org.junit.Assert.assertEquals(Assert.java:472)
at org.junit.Assert.assertEquals(Assert.java:456)
at org.apache.hadoop.ipc.TestCallQueueManager.testSwapUnderContention(TestCallQueueManager.java:215)
{noformat}
> TestCallQueueManager is still flaky
> -----------------------------------
>
> Key: HADOOP-10473
> URL: https://issues.apache.org/jira/browse/HADOOP-10473
> Project: Hadoop Common
> Issue Type: Bug
> Components: test
> Reporter: Tsz Wo Nicholas Sze
> Assignee: Tsz Wo Nicholas Sze
> Priority: Minor
>
> testSwapUnderContention counts the calls and then interrupts as shown below. There could be call after counting the call but before interrupt.
> {code}
> for (Taker t : consumers) {
> totalCallsConsumed += t.callsTaken;
> threads.get(t).interrupt();
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)