[
https://issues.apache.org/jira/browse/HADOOP-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595472#action_12595472
]
Hadoop QA commented on HADOOP-3309:
-----------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12381723/HADOOP-3309-1.patch
against trunk revision 654315.
+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 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/2434/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2434/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2434/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2434/console
This message is automatically generated.
> Unit test fails on Windows: org.apache.hadoop.mapred.TestMiniMRDFSSort.unknown
> ------------------------------------------------------------------------------
>
> Key: HADOOP-3309
> URL: https://issues.apache.org/jira/browse/HADOOP-3309
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.18.0
> Environment: windows
> Reporter: Mukund Madhugiri
> Attachments: HADOOP-3309-1.patch, HADOOP-3309.patch
>
>
> Unit test fails on Windows: org.apache.hadoop.mapred.TestMiniMRDFSSort.unknown
> *Recent changes:*
> # HADOOP-3061. Writable types for doubles and bytes.
> # HADOOP-3300. Fix locking of explicit locks in NetworkTopology.
> # HADOOP-2910. Throttle IPC Clients during bursts of requests or server
> slowdown. Clients retry connection for up to 15 minutes when socket
> connection times out.
> # HADOOP-3285. Fix input split locality when the splits align to fsblocks.
> # HADOOP-3127. Deleting files in trash should really remove them.
> # HADOOP-3268. file:// URLs issue in TestUrlStreamHandler under Windows.
> # HADOOP-1979. Speed up fsck by adding a buffered stream.
> *Failed due to timeout*
> junit.framework.AssertionFailedError: Timeout occurred
> *Output from the console before it timed out:*
> [junit] 2008-04-24 13:24:09,556 INFO util.Container
> (Container.java:stop(156)) - Stopped [EMAIL PROTECTED]
> [junit] 2008-04-24 13:24:09,696 INFO util.Container
> (Container.java:stop(156)) - Stopped WebApplicationContext[/,/]
> [junit] 2008-04-24 13:24:09,852 INFO util.Container
> (Container.java:stop(156)) - Stopped HttpContext[/logs,/logs]
> [junit] 2008-04-24 13:24:10,009 INFO util.Container
> (Container.java:stop(156)) - Stopped HttpContext[/static,/static]
> [junit] 2008-04-24 13:24:10,009 INFO util.Container
> (Container.java:stop(156)) - Stopped [EMAIL PROTECTED]
> [junit] 2008-04-24 13:24:10,009 INFO fs.FSNamesystem
> (FSEditLog.java:printStatistics(849)) - Number of transactions: 310 Total
> time for transactions(ms): 62 Number of syncs: 254 SyncTimes(ms): 23395 20970
> [junit] 2008-04-24 13:24:10,071 ERROR fs.FSNamesystem
> (FSNamesystem.java:run(1963)) - java.lang.InterruptedException
> [junit] at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(AbstractQueuedSynchronizer.java:1741)
> [junit] at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1774)
> [junit] at
> java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:359)
> [junit] at
> org.apache.hadoop.dfs.FSNamesystem$ResolutionMonitor.run(FSNamesystem.java:1940)
> [junit] at java.lang.Thread.run(Thread.java:595)
> [junit] 2008-04-24 13:24:10,321 INFO ipc.Server (Server.java:stop(1001)) -
> Stopping server on 3903
> [junit] 2008-04-24 13:24:10,321 INFO ipc.Server (Server.java:run(336)) -
> Stopping IPC Server listener on 3903
> [junit] 2008-04-24 13:24:10,321 INFO ipc.Server (Server.java:run(506)) -
> Stopping IPC Server Responder
> [junit] 2008-04-24 13:24:10,321 INFO mapred.MiniMRCluster
> (MiniMRCluster.java:waitUntilIdle(231)) - Waiting for task tracker
> tracker_buildsystem:localhost/127.0.0.1:3943 to be idle.
> [junit] 2008-04-24 13:24:10,321 INFO ipc.Server (Server.java:run(927)) - IPC
> Server handler 0 on 3903: exiting
> [junit] 2008-04-24 13:24:10,321 INFO ipc.Server (Server.java:run(927)) - IPC
> Server handler 1 on 3903: exiting
> [junit] 2008-04-24 13:24:10,321 INFO ipc.Server (Server.java:run(927)) - IPC
> Server handler 2 on 3903: exiting
> [junit] 2008-04-24 13:24:10,337 INFO ipc.Server (Server.java:run(927)) - IPC
> Server handler 9 on 3903: exiting
> [junit] 2008-04-24 13:24:10,337 INFO ipc.Server (Server.java:run(927)) - IPC
> Server handler 3 on 3903: exiting
> [junit] 2008-04-24 13:24:10,337 INFO ipc.Server (Server.java:run(927)) - IPC
> Server handler 4 on 3903: exiting
> [junit] 2008-04-24 13:24:10,337 INFO ipc.Server (Server.java:run(927)) - IPC
> Server handler 5 on 3903: exiting
> [junit] 2008-04-24 13:24:10,337 INFO ipc.Server (Server.java:run(927)) - IPC
> Server handler 8 on 3903: exiting
> [junit] 2008-04-24 13:24:10,337 INFO ipc.Server (Server.java:run(927)) - IPC
> Server handler 6 on 3903: exiting
> [junit] 2008-04-24 13:24:10,337 INFO ipc.Server (Server.java:run(927)) - IPC
> Server handler 7 on 3903: exiting
> [junit] 2008-04-24 13:24:11,321 INFO mapred.MiniMRCluster
> (MiniMRCluster.java:waitUntilIdle(231)) - Waiting for task tracker
> tracker_buildsystem:localhost/127.0.0.1:3943 to be idle.
> [junit] 2008-04-24 13:24:12,321 INFO mapred.MiniMRCluster
> (MiniMRCluster.java:waitUntilIdle(231)) - Waiting for task tracker
> tracker_buildsystem:localhost/127.0.0.1:3943 to be idle.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
