[
https://issues.apache.org/jira/browse/ATLAS-682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272241#comment-15272241
]
ATLAS QA commented on ATLAS-682:
--------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12802383/ATLAS-682.patch
against master revision feff0cf.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
+1 checkstyle. The patch generated 0 code style errors.
{color:red}-1 findbugs{color}. The patch appears to introduce 362 new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in :
./webapp/test-output/junitreports/TEST-org.apache.atlas.web.resources.RexsterGraphJerseyResourceIT
./webapp/test-output/junitreports/TEST-org.apache.atlas.web.resources.AdminJerseyResourceIT
./webapp/test-output/junitreports/TEST-org.apache.atlas.web.resources.EntityJerseyResourceIT
./webapp/test-output/junitreports/TEST-org.apache.atlas.web.resources.MetadataDiscoveryJerseyResourceIT
./webapp/test-output/junitreports/TEST-org.apache.atlas.web.resources.TypesJerseyResourceIT
Test results:
https://builds.apache.org/job/PreCommit-ATLAS-Build/204//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/204//artifact/patchprocess/newPatchFindbugsWarningswebapp.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/204//artifact/patchprocess/newPatchFindbugsWarningscommon.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/204//artifact/patchprocess/newPatchFindbugsWarningssqoop-bridge.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/204//artifact/patchprocess/newPatchFindbugsWarningshdfs-model.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/204//artifact/patchprocess/newPatchFindbugsWarningsstorm-bridge.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/204//artifact/patchprocess/newPatchFindbugsWarningshive-bridge.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/204//artifact/patchprocess/newPatchFindbugsWarningsrepository.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/204//artifact/patchprocess/newPatchFindbugsWarningstypesystem.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/204//artifact/patchprocess/newPatchFindbugsWarningsclient.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/204//artifact/patchprocess/newPatchFindbugsWarningsnotification.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ATLAS-Build/204//artifact/patchprocess/newPatchFindbugsWarningstitan.html
Console output: https://builds.apache.org/job/PreCommit-ATLAS-Build/204//console
This message is automatically generated.
> Set HBase root dir to be relative to test target directory for
> HBaseBasedAuditRepositoryTest
> --------------------------------------------------------------------------------------------
>
> Key: ATLAS-682
> URL: https://issues.apache.org/jira/browse/ATLAS-682
> Project: Atlas
> Issue Type: Bug
> Reporter: Hemanth Yamijala
> Assignee: Shwetha G S
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-682.patch
>
>
> Sometimes when running HBaseBasedAuditRepositoryTest, the test is failing
> with a timeout. Logs reveal a specific kind of stack trace:
> {code}
> 2016-04-18 15:11:44,437 FATAL - [10.200.4.44:49249.activeMasterManager:] ~
> Unhandled exception. Starting shutdown. (HMaster:2098)
> org.apache.hadoop.hbase.util.FileSystemVersionException: HBase file layout
> needs to be upgraded. You have version null and I want version 8. Consult
> http://hbase.apache.org/book.html for further information about upgrading
> HBase. Is your hbase.rootdir valid? If so, you may need to run 'hbase hbck
> -fixVersionFile'.
> at org.apache.hadoop.hbase.util.FSUtils.checkVersion(FSUtils.java:677)
> at
> org.apache.hadoop.hbase.master.MasterFileSystem.checkRootDir(MasterFileSystem.java:455)
> at
> org.apache.hadoop.hbase.master.MasterFileSystem.createInitialFileSystemLayout(MasterFileSystem.java:146)
> at
> org.apache.hadoop.hbase.master.MasterFileSystem.<init>(MasterFileSystem.java:126)
> at
> org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:649)
> at org.apache.hadoop.hbase.master.HMaster.access$500(HMaster.java:182)
> at org.apache.hadoop.hbase.master.HMaster$1.run(HMaster.java:1646)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> It appears that the HBase root directory is being set to
> /tmp/hbase-{username} and if this has left over data it is failing. Under Mac
> OSX - this is resolving to a very hard to find directory by itself. Filing
> this to see if we can fix the temporary directories to be under the target
> folder of the module so that mvn clean actually will fix problems.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
