You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Chesnay Schepler (JIRA)" <ji...@apache.org> on 2019/05/15 06:36:00 UTC

[jira] [Closed] (FLINK-12475) CommonTestUtils#printLog4jDebugConfig() should include timestamp

     [ https://issues.apache.org/jira/browse/FLINK-12475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chesnay Schepler closed FLINK-12475.
------------------------------------
    Resolution: Fixed

master: b12e37728b701573f58b297ab96984bd63042594

> CommonTestUtils#printLog4jDebugConfig() should include timestamp
> ----------------------------------------------------------------
>
>                 Key: FLINK-12475
>                 URL: https://issues.apache.org/jira/browse/FLINK-12475
>             Project: Flink
>          Issue Type: Improvement
>          Components: Test Infrastructure
>    Affects Versions: 1.9.0
>            Reporter: Chesnay Schepler
>            Assignee: Chesnay Schepler
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.9.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> {{CommonTestUtils#printLog4jDebugConfig()}} is used by a few tests to generate a log4j configuration for external processes.
> We should include a timestamp in each message. This would make it easier to figure out in which order operations between different processes occurred.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)