[jira] [Updated] (HADOOP-10395) TestCallQueueManager is flaky

2014-03-10 Thread Tsz Wo Nicholas Sze (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HADOOP-10395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze updated HADOOP-10395:
-

Priority: Minor  (was: Major)
Assignee: Arpit Agarwal
Hadoop Flags: Reviewed

+1 patch looks good.

 TestCallQueueManager is flaky
 -

 Key: HADOOP-10395
 URL: https://issues.apache.org/jira/browse/HADOOP-10395
 Project: Hadoop Common
  Issue Type: Bug
  Components: test
Affects Versions: 2.4.0
Reporter: Arpit Agarwal
Assignee: Arpit Agarwal
Priority: Minor
 Attachments: HADOOP-10395.01.patch


 {{TestCallQueueManager#testSwapUnderContention}} fails occasionally on a test 
 VM with this assert.
 {code}
 java.lang.AssertionError: null
   at org.junit.Assert.fail(Assert.java:92)
   at org.junit.Assert.assertTrue(Assert.java:43)
   at org.junit.Assert.assertTrue(Assert.java:54)
   at 
 org.apache.hadoop.ipc.TestCallQueueManager.testSwapUnderContention(TestCallQueueManager.java:193)
 {code}
 Although it appears unlikely, it is possible for the queue to be 
 intermittently empty while the putters and getters are running. The assert 
 can be removed or coded differently.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (HADOOP-10395) TestCallQueueManager is flaky

2014-03-10 Thread Arpit Agarwal (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HADOOP-10395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arpit Agarwal updated HADOOP-10395:
---

   Resolution: Fixed
Fix Version/s: 2.4.0
   3.0.0
   Status: Resolved  (was: Patch Available)

Thanks Nicholas! Committed to trunk through branch-2.4.

 TestCallQueueManager is flaky
 -

 Key: HADOOP-10395
 URL: https://issues.apache.org/jira/browse/HADOOP-10395
 Project: Hadoop Common
  Issue Type: Bug
  Components: test
Affects Versions: 2.4.0
Reporter: Arpit Agarwal
Assignee: Arpit Agarwal
Priority: Minor
 Fix For: 3.0.0, 2.4.0

 Attachments: HADOOP-10395.01.patch


 {{TestCallQueueManager#testSwapUnderContention}} fails occasionally on a test 
 VM with this assert.
 {code}
 java.lang.AssertionError: null
   at org.junit.Assert.fail(Assert.java:92)
   at org.junit.Assert.assertTrue(Assert.java:43)
   at org.junit.Assert.assertTrue(Assert.java:54)
   at 
 org.apache.hadoop.ipc.TestCallQueueManager.testSwapUnderContention(TestCallQueueManager.java:193)
 {code}
 Although it appears unlikely, it is possible for the queue to be 
 intermittently empty while the putters and getters are running. The assert 
 can be removed or coded differently.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (HADOOP-10395) TestCallQueueManager is flaky

2014-03-10 Thread Arpit Agarwal (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HADOOP-10395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arpit Agarwal updated HADOOP-10395:
---

Target Version/s: 2.4.0

 TestCallQueueManager is flaky
 -

 Key: HADOOP-10395
 URL: https://issues.apache.org/jira/browse/HADOOP-10395
 Project: Hadoop Common
  Issue Type: Bug
  Components: test
Affects Versions: 2.4.0
Reporter: Arpit Agarwal
Assignee: Arpit Agarwal
Priority: Minor
 Fix For: 3.0.0, 2.4.0

 Attachments: HADOOP-10395.01.patch


 {{TestCallQueueManager#testSwapUnderContention}} fails occasionally on a test 
 VM with this assert.
 {code}
 java.lang.AssertionError: null
   at org.junit.Assert.fail(Assert.java:92)
   at org.junit.Assert.assertTrue(Assert.java:43)
   at org.junit.Assert.assertTrue(Assert.java:54)
   at 
 org.apache.hadoop.ipc.TestCallQueueManager.testSwapUnderContention(TestCallQueueManager.java:193)
 {code}
 Although it appears unlikely, it is possible for the queue to be 
 intermittently empty while the putters and getters are running. The assert 
 can be removed or coded differently.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (HADOOP-10395) TestCallQueueManager is flaky

2014-03-09 Thread Arpit Agarwal (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HADOOP-10395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arpit Agarwal updated HADOOP-10395:
---

Attachment: HADOOP-10395.01.patch

Attaching proposed fix that removes the assert. I don't think it is necessary 
for the test.

 TestCallQueueManager is flaky
 -

 Key: HADOOP-10395
 URL: https://issues.apache.org/jira/browse/HADOOP-10395
 Project: Hadoop Common
  Issue Type: Bug
  Components: test
Affects Versions: 2.4.0
Reporter: Arpit Agarwal
 Attachments: HADOOP-10395.01.patch


 {{TestCallQueueManager#testSwapUnderContention}} fails occasionally on a test 
 VM with this assert.
 {code}
 java.lang.AssertionError: null
   at org.junit.Assert.fail(Assert.java:92)
   at org.junit.Assert.assertTrue(Assert.java:43)
   at org.junit.Assert.assertTrue(Assert.java:54)
   at 
 org.apache.hadoop.ipc.TestCallQueueManager.testSwapUnderContention(TestCallQueueManager.java:193)
 {code}
 Although extremely unlikely it is possible for the queue to be intermittently 
 empty while the putters and getters are running. The assert can be removed or 
 coded differently.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (HADOOP-10395) TestCallQueueManager is flaky

2014-03-09 Thread Arpit Agarwal (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HADOOP-10395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arpit Agarwal updated HADOOP-10395:
---

Description: 
{{TestCallQueueManager#testSwapUnderContention}} fails occasionally on a test 
VM with this assert.
{code}
java.lang.AssertionError: null
at org.junit.Assert.fail(Assert.java:92)
at org.junit.Assert.assertTrue(Assert.java:43)
at org.junit.Assert.assertTrue(Assert.java:54)
at 
org.apache.hadoop.ipc.TestCallQueueManager.testSwapUnderContention(TestCallQueueManager.java:193)
{code}

Although it appears unlikely, it is possible for the queue to be intermittently 
empty while the putters and getters are running. The assert can be removed or 
coded differently.


  was:
{{TestCallQueueManager#testSwapUnderContention}} fails occasionally on a test 
VM with this assert.
{code}
java.lang.AssertionError: null
at org.junit.Assert.fail(Assert.java:92)
at org.junit.Assert.assertTrue(Assert.java:43)
at org.junit.Assert.assertTrue(Assert.java:54)
at 
org.apache.hadoop.ipc.TestCallQueueManager.testSwapUnderContention(TestCallQueueManager.java:193)
{code}

Although extremely unlikely it is possible for the queue to be intermittently 
empty while the putters and getters are running. The assert can be removed or 
coded differently.



 TestCallQueueManager is flaky
 -

 Key: HADOOP-10395
 URL: https://issues.apache.org/jira/browse/HADOOP-10395
 Project: Hadoop Common
  Issue Type: Bug
  Components: test
Affects Versions: 2.4.0
Reporter: Arpit Agarwal
 Attachments: HADOOP-10395.01.patch


 {{TestCallQueueManager#testSwapUnderContention}} fails occasionally on a test 
 VM with this assert.
 {code}
 java.lang.AssertionError: null
   at org.junit.Assert.fail(Assert.java:92)
   at org.junit.Assert.assertTrue(Assert.java:43)
   at org.junit.Assert.assertTrue(Assert.java:54)
   at 
 org.apache.hadoop.ipc.TestCallQueueManager.testSwapUnderContention(TestCallQueueManager.java:193)
 {code}
 Although it appears unlikely, it is possible for the queue to be 
 intermittently empty while the putters and getters are running. The assert 
 can be removed or coded differently.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (HADOOP-10395) TestCallQueueManager is flaky

2014-03-09 Thread Arpit Agarwal (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HADOOP-10395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arpit Agarwal updated HADOOP-10395:
---

Status: Patch Available  (was: Open)

 TestCallQueueManager is flaky
 -

 Key: HADOOP-10395
 URL: https://issues.apache.org/jira/browse/HADOOP-10395
 Project: Hadoop Common
  Issue Type: Bug
  Components: test
Affects Versions: 2.4.0
Reporter: Arpit Agarwal
 Attachments: HADOOP-10395.01.patch


 {{TestCallQueueManager#testSwapUnderContention}} fails occasionally on a test 
 VM with this assert.
 {code}
 java.lang.AssertionError: null
   at org.junit.Assert.fail(Assert.java:92)
   at org.junit.Assert.assertTrue(Assert.java:43)
   at org.junit.Assert.assertTrue(Assert.java:54)
   at 
 org.apache.hadoop.ipc.TestCallQueueManager.testSwapUnderContention(TestCallQueueManager.java:193)
 {code}
 Although extremely unlikely it is possible for the queue to be intermittently 
 empty while the putters and getters are running. The assert can be removed or 
 coded differently.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (HADOOP-10395) TestCallQueueManager is flaky

2014-03-08 Thread Arpit Agarwal (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HADOOP-10395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arpit Agarwal updated HADOOP-10395:
---

Description: 
{{TestCallQueueManager#testSwapUnderContention}} fails occasionally on a test 
VM with this assert.
{code}
java.lang.AssertionError: null
at org.junit.Assert.fail(Assert.java:92)
at org.junit.Assert.assertTrue(Assert.java:43)
at org.junit.Assert.assertTrue(Assert.java:54)
at 
org.apache.hadoop.ipc.TestCallQueueManager.testSwapUnderContention(TestCallQueueManager.java:193)
{code}

Although extremely unlikely it is possible for the queue to be intermittently 
empty while the putters and getters are running. The assert can be coded 
removed or coded differently.


  was:
{{TestCallQueueManager#testSwapUnderContention}} fails occasionally on a test 
VM with this assert.
{code}
java.lang.AssertionError: null
at org.junit.Assert.fail(Assert.java:92)
at org.junit.Assert.assertTrue(Assert.java:43)
at org.junit.Assert.assertTrue(Assert.java:54)
at 
org.apache.hadoop.ipc.TestCallQueueManager.testSwapUnderContention(TestCallQueueManager.java:193)
{code}

I think the issue is that the assert is probabilistic and although extremely 
unlikely it is possible for the queue to be intermittently empty while the 
putters and getters are running.



 TestCallQueueManager is flaky
 -

 Key: HADOOP-10395
 URL: https://issues.apache.org/jira/browse/HADOOP-10395
 Project: Hadoop Common
  Issue Type: Bug
  Components: test
Affects Versions: 2.4.0
Reporter: Arpit Agarwal

 {{TestCallQueueManager#testSwapUnderContention}} fails occasionally on a test 
 VM with this assert.
 {code}
 java.lang.AssertionError: null
   at org.junit.Assert.fail(Assert.java:92)
   at org.junit.Assert.assertTrue(Assert.java:43)
   at org.junit.Assert.assertTrue(Assert.java:54)
   at 
 org.apache.hadoop.ipc.TestCallQueueManager.testSwapUnderContention(TestCallQueueManager.java:193)
 {code}
 Although extremely unlikely it is possible for the queue to be intermittently 
 empty while the putters and getters are running. The assert can be coded 
 removed or coded differently.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (HADOOP-10395) TestCallQueueManager is flaky

2014-03-08 Thread Arpit Agarwal (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HADOOP-10395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arpit Agarwal updated HADOOP-10395:
---

Description: 
{{TestCallQueueManager#testSwapUnderContention}} fails occasionally on a test 
VM with this assert.
{code}
java.lang.AssertionError: null
at org.junit.Assert.fail(Assert.java:92)
at org.junit.Assert.assertTrue(Assert.java:43)
at org.junit.Assert.assertTrue(Assert.java:54)
at 
org.apache.hadoop.ipc.TestCallQueueManager.testSwapUnderContention(TestCallQueueManager.java:193)
{code}

Although extremely unlikely it is possible for the queue to be intermittently 
empty while the putters and getters are running. The assert can be removed or 
coded differently.


  was:
{{TestCallQueueManager#testSwapUnderContention}} fails occasionally on a test 
VM with this assert.
{code}
java.lang.AssertionError: null
at org.junit.Assert.fail(Assert.java:92)
at org.junit.Assert.assertTrue(Assert.java:43)
at org.junit.Assert.assertTrue(Assert.java:54)
at 
org.apache.hadoop.ipc.TestCallQueueManager.testSwapUnderContention(TestCallQueueManager.java:193)
{code}

Although extremely unlikely it is possible for the queue to be intermittently 
empty while the putters and getters are running. The assert can be coded 
removed or coded differently.



 TestCallQueueManager is flaky
 -

 Key: HADOOP-10395
 URL: https://issues.apache.org/jira/browse/HADOOP-10395
 Project: Hadoop Common
  Issue Type: Bug
  Components: test
Affects Versions: 2.4.0
Reporter: Arpit Agarwal

 {{TestCallQueueManager#testSwapUnderContention}} fails occasionally on a test 
 VM with this assert.
 {code}
 java.lang.AssertionError: null
   at org.junit.Assert.fail(Assert.java:92)
   at org.junit.Assert.assertTrue(Assert.java:43)
   at org.junit.Assert.assertTrue(Assert.java:54)
   at 
 org.apache.hadoop.ipc.TestCallQueueManager.testSwapUnderContention(TestCallQueueManager.java:193)
 {code}
 Although extremely unlikely it is possible for the queue to be intermittently 
 empty while the putters and getters are running. The assert can be removed or 
 coded differently.



--
This message was sent by Atlassian JIRA
(v6.2#6252)