nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MINIFI-304) Test Failures manifested by logger initialization failures.
Date Wed, 17 May 2017 13:50:04 GMT

    [ https://issues.apache.org/jira/browse/MINIFI-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16014079#comment-16014079
] 

ASF GitHub Bot commented on MINIFI-304:
---------------------------------------

Github user kevdoran commented on the issue:

    https://github.com/apache/nifi-minifi-cpp/pull/96
  
    @aldrin I created MINIFI-319 to track the CMake Catch scanning.


> Test Failures manifested by logger initialization failures. 
> ------------------------------------------------------------
>
>                 Key: MINIFI-304
>                 URL: https://issues.apache.org/jira/browse/MINIFI-304
>             Project: Apache NiFi MiNiFi
>          Issue Type: Bug
>          Components: C++
>            Reporter: marco polo
>            Assignee: marco polo
>
> statics within spdlog would not be initialized in time depending on the order of execution.
As a result it is better to use no logging unless necessary. There are examples which use
logging, but unless explicitly needed ( and captured into strings, for example ) we should
instead turn logging off.
> Breaking this out into separate executables would be idea. This ticket will involve editing
the cmake file to move tests into a separate file. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message