Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
HBase, mail # dev - Re: Build failed in Jenkins: HBase-TRUNK #3498


Copy link to this message
-
Re: Build failed in Jenkins: hbase-0.95 #38
ramkrishna vasudevan 2013-03-08, 17:26
The test output logs are messy in the sense, we get scanner retries, time
outs and such things.

Regards
Ram

On Fri, Mar 8, 2013 at 10:53 PM, Stack <[EMAIL PROTECTED]> wrote:

> On Fri, Mar 8, 2013 at 12:58 AM, Apache Jenkins Server <
> [EMAIL PROTECTED]> wrote:
>
> > See <https://builds.apache.org/job/hbase-0.95/38/changes>
> >
> > Changes:
> >
> > [tedyu] HBASE-7960 Addendum simplify test path as suggested by Stack
> >
> > [tedyu] HBASE-7960 cleanup TestDir in TestHalfStoreFileReader (Liang Xie)
> >
> > [apurtell] HBASE-8004. Creating an existing table from Shell does not
> > throw TableExistsException (Jeffrey Zhong)
> >
> >
> ....
>
>
> >
> > Results :
> >
> > Failed tests:
> >
> testCyclicReplication(org.apache.hadoop.hbase.replication.TestMasterReplication):
> > Waited too much time for put replication
> >
> >
> testMultiSlaveReplication(org.apache.hadoop.hbase.replication.TestMultiSlaveReplication):
> > Waited too much time for put replication
> >
> > Tests in error:
> >
> >
> testDelayedRpcImmediateReturnValue(org.apache.hadoop.hbase.ipc.TestDelayedRpc):
> > Index: 0, Size: 0
> >
> loadTest[0](org.apache.hadoop.hbase.util.TestMiniClusterLoadSequential):
> > test timed out after 180000 milliseconds
> >
> loadTest[1](org.apache.hadoop.hbase.util.TestMiniClusterLoadSequential):
> > test timed out after 180000 milliseconds
> >
> loadTest[2](org.apache.hadoop.hbase.util.TestMiniClusterLoadSequential):
> > test timed out after 180000 milliseconds
> >   testCacheSeqNums(org.apache.hadoop.hbase.client.TestHCM): test timed
> out
> > after 60000 milliseconds
> >   testRegionCaching(org.apache.hadoop.hbase.client.TestHCM): test timed
> > out after 60000 milliseconds
> >   test3686a(org.apache.hadoop.hbase.client.TestScannerTimeout): 19402ms
> > passed since the last invocation, timeout is currently set to 15000
> >
> >
> testScannerNextRPCTimesout(org.apache.hadoop.hbase.client.TestClientScannerRPCTimeout):
> > Failed after attempts=3, exceptions:(..)
> >   testBatchWithPut(org.apache.hadoop.hbase.client.TestMultiParallel):
> > Failed 98 actions: ExecutionException: 98 times,
> >
> >
> loadTest[0](org.apache.hadoop.hbase.io.encoding.TestLoadAndSwitchEncodeOnDisk):
> > test timed out after 180000 milliseconds
> >   org.apache.hadoop.hbase.rest.TestMultiRowResource: Shutting down
> >   org.apache.hadoop.hbase.rest.client.TestRemoteTable: Shutting down
> >   org.apache.hadoop.hbase.rest.client.TestRemoteTable
> >   org.apache.hadoop.hbase.rest.TestRowResource: Shutting down
> >
> >
> testSimpleZKCohortMemberController(org.apache.hadoop.hbase.procedure.TestZKProcedureControllers):
> > test timed out after 15000 milliseconds
> >
> >
> testRestoreSnapshotOfCloned(org.apache.hadoop.hbase.snapshot.TestRestoreFlushSnapshotFromClient):
> > org.apache.hadoop.hbase.exceptions.SnapshotDoesNotExistException:
> Snapshot
> > 'snaptb1-1362732524988' doesn't exist on the filesystem
> >
> > Tests run: 1181, Failures: 2, Errors: 15, Skipped: 7
> >
>
> This is a bunch of failures.  It is a reverse of the trend where we were
> heading toward zero.   Build #39 is running now.  Lets see what it says.
>  Will start backing out the above changes to see which brought on the
> above.
>
> Thanks,
> St.Ack
>