It seems like changes that involve multiple modules are failing consistently.

https://issues.apache.org/jira/browse/HDFS-9241?focusedCommentId=14968008&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14968008
https://issues.apache.org/jira/browse/HADOOP-12500?focusedCommentId=14968065&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14968065

Looks like a bug?

~Haohui

On Tue, Oct 20, 2015 at 2:23 AM, Steve Loughran <ste...@hortonworks.com> wrote:
>
>> On 19 Oct 2015, at 19:09, Andrew Wang <andrew.w...@cloudera.com> wrote:
>>
>> These tests should still be fixed up to use target/ instead of
>> build/test/data though. Steve, I'm happy to review if you're chasing these
>> down, or we could trade roles.
>
> I'm not going to look at it today, I've pushed up the branch to github if you 
> want to start with it
>
> https://github.com/steveloughran/hadoop-trunk/tree/stevel/HDFS-9263_build_test_data
>
> Looking at the test runs (I didn't run them locally as I now appear to run 
> out of file handles), It's clear that some of the tests expect restarted mini 
> dfs clusters to always use the same path; adding a random subdir there is 
> breaking things.
>
>
>
> 2015-10-20 03:54:11,141 [main] WARN  namenode.FSNamesystem 
> (FSNamesystem.java:loadFromDisk(682)) - Encountered exception loading fsimage
> org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory 
> /testptch/hadoop/hadoop-hdfs-project/hadoop-hdfs/target/test/data/3/TzpG5hegiz/name-0-1
>  is in an inconsistent state: storage directory does not exist or is not 
> accessible.
>         at 
> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverStorageDirs(FSImage.java:323)
>         at 
> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:211)
>         at 
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:973)
>         at 
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:680)
>         at 
> org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:571)
>         at 
> org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:628)
>         at 
> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:833)
>         at 
> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:812)
>         at 
> org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1505)
>         at 
> org.apache.hadoop.hdfs.MiniDFSCluster.createNameNode(MiniDFSCluster.java:1247)
>         at 
> org.apache.hadoop.hdfs.MiniDFSCluster.configureNameService(MiniDFSCluster.java:1016)
>         at 
> org.apache.hadoop.hdfs.MiniDFSCluster.createNameNodesAndSetConf(MiniDFSCluster.java:888)
>         at 
> org.apache.hadoop.hdfs.MiniDFSCluster.initMiniDFSCluster(MiniDFSCluster.java:820)
>         at 
> org.apache.hadoop.hdfs.MiniDFSCluster.<init>(MiniDFSCluster.java:479)
>         at 
> org.apache.hadoop.hdfs.MiniDFSCluster$Builder.build(MiniDFSCluster.java:438)
>         at 
> org.apache.hadoop.hdfs.TestSetTimes.testTimes(TestSetTimes.java:197)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>         at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>         at java.lang.reflect.Method.invoke(Method.java:497)
>         at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
>         at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>         at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
>         at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>         at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
>         at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
>         at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
>         at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
>         at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
>         at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
>         at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
>         at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
>         at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
>         at 
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
>         at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
>         at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
>         at 
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
>         at 
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
>         at 
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)

Reply via email to