[
https://issues.apache.org/jira/browse/HADOOP-14573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16065705#comment-16065705
]
Hudson commented on HADOOP-14573:
---------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11936 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/11936/])
HADOOP-14573. regression: Azure tests which capture logs failing with (liuml07:
rev 686a634f01e454537d1a9d531330e60a60233ca4)
* (edit)
hadoop-tools/hadoop-azure/src/test/java/org/apache/hadoop/fs/azure/TestFileSystemOperationsWithThreads.java
* (edit)
hadoop-tools/hadoop-azure/src/test/java/org/apache/hadoop/fs/azure/TestNativeAzureFileSystemClientLogging.java
> 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
> Fix For: 2.9.0, 3.0.0-alpha4
>
> 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: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
