[
https://issues.apache.org/jira/browse/HBASE-12022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139406#comment-14139406
]
Hadoop QA commented on HBASE-12022:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12669782/HBASE-12022.patch
against trunk revision .
ATTACHMENT ID: 12669782
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/10973//console
This message is automatically generated.
> Payloads on Failure attempt to serialize the byte[] into strings...
> -------------------------------------------------------------------
>
> Key: HBASE-12022
> URL: https://issues.apache.org/jira/browse/HBASE-12022
> Project: HBase
> Issue Type: Bug
> Components: IPC/RPC
> Affects Versions: 0.94.23
> Reporter: Vladimir Rodionov
> Assignee: Vladimir Rodionov
> Priority: Trivial
> Fix For: 0.94.24
>
> Attachments: HBASE-12022.patch
>
>
> HBaseServer$HandlerRun
> LOG.debug(getName()", call "+call": error: " + e, e);
> errorClass = e.getClass().getName();
> error = StringUtils.stringifyException(e);
> Whether or not we are at a debug level, we will serialize the call... Our
> call has a shit load of KVPairs as byte[]... These need to be at least
> wrapped in LOG.isDebugEnabled blocks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
