[
https://issues.apache.org/jira/browse/HADOOP-14573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HADOOP-14573:
------------------------------------
Attachment: HADOOP-14573-002.patch
Patch 002; fix checkstyles
tested the two specific tests the patches touch, Azure lreland
{code}
-------------------------------------------------------
Running org.apache.hadoop.fs.azure.TestFileSystemOperationsWithThreads
Tests run: 19, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 228.027 sec -
in org.apache.hadoop.fs.azure.TestFileSystemOperationsWithThreads
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.apache.hadoop.fs.azure.TestNativeAzureFileSystemClientLogging
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.553 sec - in
org.apache.hadoop.fs.azure.TestNativeAzureFileSystemClientLogging
Results :
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
{code}
> 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
> Assignee: Steve Loughran
> Attachments: HADOOP-14573-001.patch, HADOOP-14573-002.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]