[
https://issues.apache.org/jira/browse/HBASE-10154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13853120#comment-13853120
]
stack commented on HBASE-10154:
-------------------------------
I tried it and got this:
{code}
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.apache.hadoop.hbase.tool.TestCanary
2013-12-19 10:29:35.168 java[59546:1003] Unable to load realm info from
SCDynamicStore
org.apache.maven.surefire.booter.SurefireBooterForkException: Error occurred in
starting fork, check output in log
at
org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:238)
at
org.apache.maven.plugin.surefire.booterclient.ForkStarter.access$000(ForkStarter.java:64)
at
org.apache.maven.plugin.surefire.booterclient.ForkStarter$ParallelFork.call(ForkStarter.java:303)
at
org.apache.maven.plugin.surefire.booterclient.ForkStarter$ParallelFork.call(ForkStarter.java:285)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:695)
No results for java.util.concurrent.FutureTask@1100d290
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
{code}
No tests ran and I got the above output.
Did I do it wrong [~takeshi.miao] Thanks.
> Add a unit test for Canary tool
> -------------------------------
>
> Key: HBASE-10154
> URL: https://issues.apache.org/jira/browse/HBASE-10154
> Project: HBase
> Issue Type: Improvement
> Components: monitoring, test
> Reporter: takeshi.miao
> Assignee: takeshi.miao
> Priority: Minor
> Fix For: 0.99.0
>
> Attachments: HBASE-10154-trunk-v01.patch, HBASE-10154-trunk-v02.patch
>
>
> Due to HBASE-10108, I am working to come out a unit test for
> o.h.hbase.tool.Canary to eliminate this kind of issue.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
