[
https://issues.apache.org/jira/browse/HDFS-6515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14186625#comment-14186625
]
Tony Reix commented on HDFS-6515:
---------------------------------
Hello
Reading the console output, I see nothing related to the patch that could be
the root cause of the failure.
The error seems to be around:
HDFS-6515 patch is being downloaded at Mon Oct 27 07:51:14 UTC 2014 from
http://issues.apache.org/jira/secure/attachment/12654094/HDFS-6515-1.patch
cp: cannot stat '/home/jenkins/buildSupport/lib/*': No such file or directory
The patch does not appear to apply with p0 to p2
PATCH APPLICATION FAILED
where the error deals with some lib stored in Jenkins directory.
On my side, I gonna check that the patch works fine on the branch 'trunk'.
> testPageRounder (org.apache.hadoop.hdfs.server.datanode.TestFsDatasetCache)
> -----------------------------------------------------------------------------
>
> Key: HDFS-6515
> URL: https://issues.apache.org/jira/browse/HDFS-6515
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: datanode
> Affects Versions: 3.0.0, 2.4.0
> Environment: Linux on PPC64
> Tested with Hadoop 3.0.0 SNAPSHOT, on RHEL 6.5, on Ubuntu 14.04, on Fedora
> 19, using mvn -Dtest=TestFsDatasetCache#testPageRounder -X test
> Reporter: Tony Reix
> Priority: Blocker
> Labels: test
> Attachments: HDFS-6515-1.patch
>
>
> I have an issue with test :
> testPageRounder
> (org.apache.hadoop.hdfs.server.datanode.TestFsDatasetCache)
> on Linux/PowerPC.
> On Linux/Intel, test runs fine.
> On Linux/PowerPC, I have:
> testPageRounder(org.apache.hadoop.hdfs.server.datanode.TestFsDatasetCache)
> Time elapsed: 64.037 sec <<< ERROR!
> java.lang.Exception: test timed out after 60000 milliseconds
> Looking at details, I see that some "Failed to cache " messages appear in the
> traces. Only 10 on Intel, but 186 on PPC64.
> On PPC64, it looks like some thread is waiting for something that never
> happens, generating a TimeOut.
> I'm now using IBM JVM, however I've just checked that the issue also appears
> with OpenJDK.
> I'm now using Hadoop latest, however, the issue appeared within Hadoop 2.4.0 .
> I need help for understanding what the test is doing, what traces are
> expected, in order to understand what/where is the root cause.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
