I think only client.TestAdmin is common.

In trunk, Karthick noticed this on Friday:
"Test set: org.apache.hadoop.hbase.
master.TestCatalogJanitor
-------------------------------------------------------------------------------
Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.539 sec
<<< FAILURE!
testCleanParent(org.apache.hadoop.hbase.master.TestCatalogJanitor)  Time
elapsed: 0.329 sec  <<< ERROR!
java.lang.NullPointerException
        at
org.apache.hadoop.hbase.master.SplitLogManager.finishInitialization(SplitLogManager.java:161)
        at
org.apache.hadoop.hbase.master.MasterFileSystem.<init>(MasterFileSystem.java:99)
        at
org.apache.hadoop.hbase.master.TestCatalogJanitor$MockMasterServices.<init>(TestCatalogJanitor.java:120)
        at
org.apache.hadoop.hbase.master.TestCatalogJanitor.testCleanParent(TestCatalogJanitor.java:215)

Not sure how this test ever worked, because the zookeeper watcher is never
initialized in this call stack.

Best Regards,
Karthick Sankarachary"


On Mon, Apr 25, 2011 at 3:15 PM, Stack <[email protected]> wrote:

> Both test failures are in trunk and branch?
> St.Ack
>
> On Mon, Apr 25, 2011 at 3:10 PM, Ted Yu <[email protected]> wrote:
> > The following test failure appears in both 0.90 and trunk.
> >
> > FYI
> >
> > ---------- Forwarded message ----------
> > From: Apache Jenkins Server <[email protected]>
> > Date: Mon, Apr 25, 2011 at 2:59 PM
> > Subject: Build failed in Jenkins: hbase-0.90 #165
> > To: [email protected]
> >
> >
> > See <https://builds.apache.org/hudson/job/hbase-0.90/165/changes>
> >
> > Changes:
> >
> > [stack] HBASE-3634 Fix JavaDoc for put(List<Put> puts) in HTableInterface
> >
> > [stack] HBASE-2470 Add Scan.setTimeRange() support in Shell
> >
> > [stack] HBASE-3539 Improve shell help to reflect all possible options
> >
> > [stack] HBASE-3817 HBase Shell has an issue accepting FILTER for the
> 'scan'
> > command.
> >
> > ------------------------------------------
> > Running org.apache.hadoop.hbase.
> > client.TestAdmin
> > Tests run: 16, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 235.587
> sec
> > <<< FAILURE!
> >
>

Reply via email to