[
https://issues.apache.org/jira/browse/HADOOP-5114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670626#action_12670626
]
Hadoop QA commented on HADOOP-5114:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12399480/HADOOP-5114.patch
against trunk revision 740532.
+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 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 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 failed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3799/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3799/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3799/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3799/console
This message is automatically generated.
> A bunch of mapred unit tests are failing on Windows
> ---------------------------------------------------
>
> Key: HADOOP-5114
> URL: https://issues.apache.org/jira/browse/HADOOP-5114
> Project: Hadoop Core
> Issue Type: Test
> Components: mapred, test
> Affects Versions: 0.18.3
> Environment: Windows
> Reporter: Ramya R
> Assignee: Raghu Angadi
> Priority: Minor
> Fix For: 0.18.4
>
> Attachments: HADOOP-5114-branch-18.patch,
> HADOOP-5114-branch-18.patch, HADOOP-5114.patch, HADOOP-5114.patch,
> HADOOP-5114.patch, HADOOP-5114.patch, LOGS.zip, tmp.log
>
>
> A bunch of unit tests are consistently failing when run on Windows. Below are
> a list of unit tests which are failing and the corresponding exceptions
> thrown:
> Exception: "java.net.ConnectException: Connection refused: no further
> information"
> Failing tests:
> * TestMiniMRMapRedDebugScript - testMapDebugScript
> * TestNoDefaultsJobConf - testNoDefaults
> * TestQueueManager - testAllEnabledACLForJobSubmission
> * TestCompressedEmptyMapOutputs -
> testMapReduceSortWithCompressedEmptyMapOutputs
> * TestJobInProgressListener - testJobQueueChanges
> * TestKillCompletedJob - testKillCompJob
> * TestMiniMRClasspath - testClassPath
> * TestMiniMRDFSCaching - testWithDFS
> * TestMiniMRWithDFSWithDistinctUsers - testDistinctUsers
> * TestSetupAndCleanupFailure - testWithDFS
> * TestDBJob - testRun
> * TestMiniMRWithDFS - testWithDFS
> * TestJobStatusPersistency - testNonPersistency
> * TestSpecialCharactersInOutputPath - testJobWithDFS
> * TestUserDefinedCounters - testMapReduceJob
> * TestDelegatingInputFormat - testSplitting
> * TestEmptyJobWithDFS - testEmptyJobWithDFS
> * TestJavaSerialization - testMapReduceJob
> * TestClusterMapReduceTestCase - testMapReduce
> Exception: java.lang.IllegalArgumentException: Pathname /<path> from <path>
> is not a valid DFS filename.
> Failing tests:
> * TestJobInProgress - testRunningTaskCount
> * TestJobQueueInformation - testJobQueues
> * TestJobTrackerRestart - testJobTrackerRestart
> Exception: java.io.IOException: Bad connect ack with firstBadLink
> 127.0.0.1:<port number>
> Failing tests:
> * TestJobSysDirWithDFS - testWithDFS
> * TestJobInProgress - testPendingMapTaskCount
> * TestMiniMRDFSSort - testMapReduceSort
> Exception: junit.framework.AssertionFailedError
> Failing tests:
> * TestMRServerPorts - testJobTrackerPorts
> * TestMRServerPorts - testTaskTrackerPorts
> * TestMiniMRTaskTempDir - testTaskTempDir
> Exception: java.io.IOException: Job failed!
> Failing tests:
> * TestMiniMRLocalFS - testWithLocal
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
