[
https://issues.apache.org/jira/browse/HADOOP-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606620#action_12606620
]
Hadoop QA commented on HADOOP-3603:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12384335/3603-0.patch
against trunk revision 669646.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
-1 javac. The applied patch generated 445 javac compiler warnings (more
than the trunk's current 444 warnings).
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2703/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2703/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2703/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2703/console
This message is automatically generated.
> Setting spill threshold to 100% fails to detect spill for records
> -----------------------------------------------------------------
>
> Key: HADOOP-3603
> URL: https://issues.apache.org/jira/browse/HADOOP-3603
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.17.0
> Reporter: Chris Douglas
> Assignee: Chris Douglas
> Priority: Blocker
> Fix For: 0.18.0
>
> Attachments: 3603-0.patch
>
>
> If io.sort.record.percent is set to 1.0, the simultaneous collection and
> spill is disabled. However, if one exhausts the offset allocation before the
> serialization allocation, the limit will not be detected and the write will
> block forever.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
