[
https://issues.apache.org/jira/browse/HBASE-22545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16860633#comment-16860633
]
Mingliang Liu commented on HBASE-22545:
---------------------------------------
[~elserj] I think I have some context from Hadoop side. [HADOOP-12897] wraps
the initial exception within {{KerberosAuthenticator#authenticate}} so we
should check the cause of exception when calling
{{GenericTestUtils#assertExceptionContains(String, Throwable)}}. Since
[HADOOP-12897] is committed to Hadoop 3 only and I'm not sure should we include
that in Hadoop 2.8, I guess the easy fix is for this test. We can make it work
for both Hadoop 2 and Hadoop 3 if we check both the exception and its cause.
I attach a patch implementing this which is tested with {{mvn test
-Dtest=TestLogLevel}} and {{mvn test -Dtest=TestLogLevel -Dhadoop.profile=3.0}}
locally and they pass. Let me know if it works for you, thanks!
> TestLogLevel broken
> -------------------
>
> Key: HBASE-22545
> URL: https://issues.apache.org/jira/browse/HBASE-22545
> Project: HBase
> Issue Type: Bug
> Components: test
> Reporter: Josh Elser
> Assignee: Josh Elser
> Priority: Major
>
> I think I might have broken TestLogLevel on Hadoop 3 in HBASE-22467.
> ca00cbeed21c639622b86967d82a70338689b347 seems to fail consistently but
> 1c1638f698036d6b63cb52fb94a42464d8cc1211 is passing.
> Figure out what happened to cause this (and only on H3).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)