hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Todd Lipcon <t...@cloudera.com>
Subject Re: Hadoop-Mapreduce-trunk - Build # 622 - Still Failing
Date Thu, 17 Mar 2011 18:06:57 GMT
This failed due to TestBlockFixer:
https://issues.apache.org/jira/browse/MAPREDUCE-2395
But it didn't show up in the test results due to:
https://issues.apache.org/jira/browse/MAPREDUCE-2394

-Todd

On Thu, Mar 17, 2011 at 2:41 AM, Apache Hudson Server
<hudson@hudson.apache.org> wrote:
> See https://hudson.apache.org/hudson/job/Hadoop-Mapreduce-trunk/622/
>
> ###################################################################################
> ########################## LAST 60 LINES OF THE CONSOLE ###########################
> [...truncated 310363 lines...]
>    [junit] 11/03/17 09:38:25 INFO datanode.FSDatasetAsyncDiskService: All async disk
service threads have been shut down.
>    [junit] 11/03/17 09:38:25 WARN datanode.FSDatasetAsyncDiskService: AsyncDiskService
has already shut down.
>    [junit] 11/03/17 09:38:25 INFO hdfs.MiniDFSCluster: Shutting down DataNode 0
>    [junit] 11/03/17 09:38:26 INFO ipc.Server: Stopping server on 59253
>    [junit] 11/03/17 09:38:26 INFO ipc.Server: IPC Server handler 0 on 59253: exiting
>    [junit] 11/03/17 09:38:26 INFO ipc.Server: IPC Server handler 1 on 59253: exiting
>    [junit] 11/03/17 09:38:26 INFO ipc.Server: IPC Server handler 2 on 59253: exiting
>    [junit] 11/03/17 09:38:26 INFO ipc.Server: Stopping IPC Server Responder
>    [junit] 11/03/17 09:38:26 INFO datanode.DataNode: Waiting for threadgroup to exit,
active threads is 1
>    [junit] 11/03/17 09:38:26 INFO ipc.Server: Stopping IPC Server listener on 59253
>    [junit] 11/03/17 09:38:26 WARN datanode.DataNode: DatanodeRegistration(127.0.0.1:53867,
storageID=DS-922451314-127.0.1.1-53867-1300354704973, infoPort=57652, ipcPort=59253):DataXceiveServer:
java.nio.channels.AsynchronousCloseException
>    [junit]     at java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:185)
>    [junit]     at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:159)
>    [junit]     at sun.nio.ch.ServerSocketAdaptor.accept(ServerSocketAdaptor.java:84)
>    [junit]     at org.apache.hadoop.hdfs.server.datanode.DataXceiverServer.run(DataXceiverServer.java:134)
>    [junit]     at java.lang.Thread.run(Thread.java:662)
>    [junit]
>    [junit] 11/03/17 09:38:26 INFO datanode.DataNode: Waiting for threadgroup to exit,
active threads is 0
>    [junit] 11/03/17 09:38:26 INFO datanode.DataBlockScanner: Exiting DataBlockScanner
thread.
>    [junit] 11/03/17 09:38:26 INFO datanode.DataNode: DatanodeRegistration(127.0.0.1:53867,
storageID=DS-922451314-127.0.1.1-53867-1300354704973, infoPort=57652, ipcPort=59253):Finishing
DataNode in: FSDataset{dirpath='/grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk/trunk/build/contrib/raid/test/data/dfs/data/data1/current/finalized,/grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk/trunk/build/contrib/raid/test/data/dfs/data/data2/current/finalized'}
>    [junit] 11/03/17 09:38:26 INFO ipc.Server: Stopping server on 59253
>    [junit] 11/03/17 09:38:26 INFO datanode.DataNode: Waiting for threadgroup to exit,
active threads is 0
>    [junit] 11/03/17 09:38:26 INFO datanode.FSDatasetAsyncDiskService: Shutting down
all async disk service threads...
>    [junit] 11/03/17 09:38:26 INFO datanode.FSDatasetAsyncDiskService: All async disk
service threads have been shut down.
>    [junit] 11/03/17 09:38:26 WARN datanode.FSDatasetAsyncDiskService: AsyncDiskService
has already shut down.
>    [junit] 11/03/17 09:38:26 WARN namenode.FSNamesystem: ReplicationMonitor thread
received InterruptedException.java.lang.InterruptedException: sleep interrupted
>    [junit] 11/03/17 09:38:26 INFO namenode.FSEditLog: Number of transactions: 14 Total
time for transactions(ms): 0Number of transactions batched in Syncs: 0 Number of syncs: 7
SyncTimes(ms): 7 3
>    [junit] 11/03/17 09:38:26 WARN namenode.DecommissionManager: Monitor interrupted:
java.lang.InterruptedException: sleep interrupted
>    [junit] 11/03/17 09:38:26 INFO ipc.Server: Stopping server on 58512
>    [junit] 11/03/17 09:38:26 INFO ipc.Server: IPC Server handler 0 on 58512: exiting
>    [junit] 11/03/17 09:38:26 INFO ipc.Server: IPC Server handler 3 on 58512: exiting
>    [junit] 11/03/17 09:38:26 INFO ipc.Server: IPC Server handler 1 on 58512: exiting
>    [junit] 11/03/17 09:38:26 INFO ipc.Server: IPC Server handler 5 on 58512: exiting
>    [junit] 11/03/17 09:38:26 INFO ipc.Server: Stopping IPC Server listener on 58512
>    [junit] 11/03/17 09:38:26 INFO ipc.Server: IPC Server handler 4 on 58512: exiting
>    [junit] 11/03/17 09:38:26 INFO ipc.Server: IPC Server handler 6 on 58512: exiting
>    [junit] 11/03/17 09:38:26 INFO ipc.Server: IPC Server handler 9 on 58512: exiting
>    [junit] 11/03/17 09:38:26 INFO ipc.Server: IPC Server handler 7 on 58512: exiting
>    [junit] 11/03/17 09:38:26 INFO ipc.Server: IPC Server handler 8 on 58512: exiting
>    [junit] 11/03/17 09:38:26 INFO ipc.Server: Stopping IPC Server Responder
>    [junit] 11/03/17 09:38:26 INFO ipc.Server: IPC Server handler 2 on 58512: exiting
>    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 3.015 sec
>
> BUILD FAILED
> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk/trunk/build.xml:834: The
following error occurred while executing this line:
> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk/trunk/build.xml:818: The
following error occurred while executing this line:
> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk/trunk/src/contrib/build.xml:60:
The following error occurred while executing this line:
> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk/trunk/src/contrib/raid/build.xml:60:
Tests failed!
>
> Total time: 239 minutes 28 seconds
> [FINDBUGS] Skipping publisher since build result is FAILURE
> Recording fingerprints
> Archiving artifacts
> Recording test results
> Publishing Javadoc
> Publishing Clover coverage report...
> No Clover report will be published due to a Build Failure
> Email was triggered for: Failure
> Sending email for trigger: Failure
>
>
>
> ###################################################################################
> ############################## FAILED TESTS (if any) ##############################
> All tests passed
>



-- 
Todd Lipcon
Software Engineer, Cloudera

Mime
View raw message