You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Duo Zhang (Jira)" <ji...@apache.org> on 2022/03/05 04:07:00 UTC

[jira] [Resolved] (HBASE-26799) TestCanaryTool.testWriteTableTimeout is flaky

     [ https://issues.apache.org/jira/browse/HBASE-26799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Duo Zhang resolved HBASE-26799.
-------------------------------
    Fix Version/s: 3.0.0-alpha-3
     Hadoop Flags: Reviewed
       Resolution: Fixed

Merged to master.

Thanks [~GeorryHuang] for reviewing!

> TestCanaryTool.testWriteTableTimeout is flaky
> ---------------------------------------------
>
>                 Key: HBASE-26799
>                 URL: https://issues.apache.org/jira/browse/HBASE-26799
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Major
>             Fix For: 3.0.0-alpha-3
>
>
> {noformat}
> Wanted but not invoked:
> appender.append(<custom argument matcher>);
> -> at org.apache.hadoop.hbase.tool.TestCanaryTool.testWriteTableTimeout(TestCanaryTool.java:310)
> However, there were exactly 2 interactions with this mock:
> appender.getName();
> -> at org.apache.logging.log4j.core.config.AbstractConfiguration.addLoggerAppender(AbstractConfiguration.java:859)
> appender.getName();
> -> at org.apache.logging.log4j.core.config.AppenderControl.<init>(AppenderControl.java:56)
> {noformat}
> May be related to the recent log4j2 change.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)