You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2017/06/22 20:51:00 UTC
[jira] [Commented] (HADOOP-14573) regression:
TestNativeAzureFileSystemClientLogging failing with move to SLF4J
[ https://issues.apache.org/jira/browse/HADOOP-14573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16059987#comment-16059987 ]
Steve Loughran commented on HADOOP-14573:
-----------------------------------------
cause will be HADOOP-14296, no doubt
> regression: TestNativeAzureFileSystemClientLogging failing with move to SLF4J
> -----------------------------------------------------------------------------
>
> Key: HADOOP-14573
> URL: https://issues.apache.org/jira/browse/HADOOP-14573
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/azure, test
> Affects Versions: 2.9.0
> Reporter: Steve Loughran
>
> The test {{TestNativeAzureFileSystemClientLogging}} is failing; with some extra diagnostics it implies that the log isn't being captured.
> This test is primarily about verifying that things get logged, grabbing the log and then looking for the presence/absence of log output.
> This makes it brittle to: changes in log output, log messages, and here: log wiring.
> Do we need to retain this test at all? If yes,then log capture needs to be looked again (HADOOP-13470 covers its past). If no: delete and let's not worry about it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org