|
Should also add: no unit tests, because it's just straightforward null checks.
For Hadoop-0.20, we should think about ways of informing clients about the failures, instead of just returning silently, as Hemanth pointed out here
Some comments about this patch.
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12393039/hadoop-4420.patch against trunk revision 709040. +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 did not generate any 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 Eclipse classpath. The patch retains Eclipse classpath integrity. +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/3511/testReport/ This message is automatically generated. Added null check and log warning on jobid to getJobStatus(); also added null check in o.a.h.m.CompletedJobStore.readJobStatus() which it calls.
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12393334/hadoop-4420.patch.2 against trunk revision 720930. +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 did not generate any 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 Eclipse classpath. The patch retains Eclipse classpath integrity. -1 core tests. The patch failed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3656/testReport/ This message is automatically generated. core test failure is due to something in DFS testFileAppend – Can't see how it's related to this.
Integrated in Hadoop-trunk #680 (See http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/680/
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
HADOOP-4419at the same time