|
[ edit - nevermind ]
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12388084/3940-0.patch against trunk revision 685425. +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. -1 javadoc. The javadoc tool appears to have generated 1 warning messages. +1 javac. The applied patch does not increase the total number of javac compiler 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 failed core unit tests. -1 contrib tests. The patch failed contrib unit tests. Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3058/testReport/ This message is automatically generated. Added some comments to waitForDataToMerge, particularly explaining why numRequiredMapOutputs == 0 is a special case, per Arun's suggestion.
Test failures are due to Integrated in Hadoop-trunk #581 (See http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/581/
There was a suggestion on the list to include this in 0.18.1. That sounds right to me. Thoughts?
Integrated in Hadoop-trunk #595 (See http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/595/
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Initializing numRequiredMapOutputs to Integer.MAX_VALUE would require a different check at the end; this should handle both.