so flaky. I can't get a clean run even without this patch.
On Feb 20, 2007, at 12:53 PM, Hadoop QA (JIRA) wrote:
[ https://issues.apache.org/jira/browse/HADOOP-1025?
page=com.atlassian.jira.plugin.system.issuetabpanels:comment-
tabpanel#action_12474552 ]
Hadoop QA commented on HADOOP-1025:
-----------------------------------
-1, because 3 attempts failed to build and test the latest
attachment (http://issues.apache.org/jira/secure/attachment/
12351392/HADOOP-1025.patch) against trunk revision . Please note
that this message is automatically generated and may represent a
problem with the automation system and not the patch.
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/HADOOP-1025?
page=com.atlassian.jira.plugin.system.issuetabpanels:comment-
tabpanel#action_12474552 ]
Hadoop QA commented on HADOOP-1025:
-----------------------------------
-1, because 3 attempts failed to build and test the latest
attachment (http://issues.apache.org/jira/secure/attachment/
12351392/HADOOP-1025.patch) against trunk revision . Please note
that this message is automatically generated and may represent a
problem with the automation system and not the patch.
remove dead code in Server.java
-------------------------------
Key: HADOOP-1025
URL: https://issues.apache.org/jira/browse/
HADOOP-1025
Project: Hadoop
Issue Type: Improvement
Components: ipc
Reporter: Doug Cutting
Assigned To: Doug Cutting
Priority: Minor
Fix For: 0.12.0
Attachments: HADOOP-1025.patch
There's some dead code in Server.java. The callDequeued field is
no longer used, yet it is populated, synchronized on and notified.
---------------------------------
Key: HADOOP-1025
URL: https://issues.apache.org/jira/browse/
HADOOP-1025
Project: Hadoop
Issue Type: Improvement
Components: ipc
Reporter: Doug Cutting
Assigned To: Doug Cutting
Priority: Minor
Fix For: 0.12.0
Attachments: HADOOP-1025.patch
There's some dead code in Server.java. The callDequeued field is
no longer used, yet it is populated, synchronized on and notified.
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.