hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ramya R (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5114) A bunch of mapred unit tests are failing on Windows
Date Sun, 08 Feb 2009 13:52:59 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671587#action_12671587
] 

Ramya R commented on HADOOP-5114:
---------------------------------

bq. I ran test-core on 0.18 on windows. Two of the tests failed, but re running those succeeded
again. 
I observed the same behavior as well on 18 branch. However when I ran test-core on trunk,
I was able to see > 70 test failures out of which > 50 were mapred unit test failures.
Shall I open a new jira?

> 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-branch-18.patch,
HADOOP-5114.patch, HADOOP-5114.patch, HADOOP-5114.patch, HADOOP-5114.patch, HADOOP-5114.patch,
LOGS.zip, TEST-org.apache.hadoop.dfs.TestOverReplicatedBlocks.txt, 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.


Mime
View raw message