[
https://issues.apache.org/jira/browse/HADOOP-14573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16061523#comment-16061523
]
Steve Loughran edited comment on HADOOP-14573 at 6/23/17 9:34 PM:
------------------------------------------------------------------
HADOOP-11573: patch 001. fix log capture regression. add better assertion
reporting, then move to commons log capture,
Testing: ran these failing tests manually, then applied patch to the
HADOOP-14553 branch and all its tests completed; azure ireland
was (Author: [email protected]):
HADOOP-11573: patch 001. fix log capture regression. add better assertion
reporting, then move to commons log capture,
Testing: ran these failing tests manually, then applied patch to the
HADOOP-14553 branch and all its tests completed
> regression: Azure tests which capture logs 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
> Attachments: HADOOP-14573-001.patch
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
