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

ASF GitHub Bot updated FLINK-16237:
-----------------------------------
    Labels: pull-request-available test-stability  (was: test-stability)

> Several places missing Log4j2 configuration property
> ----------------------------------------------------
>
>                 Key: FLINK-16237
>                 URL: https://issues.apache.org/jira/browse/FLINK-16237
>             Project: Flink
>          Issue Type: Bug
>          Components: Tests
>            Reporter: Yangze Guo
>            Assignee: Chesnay Schepler
>            Priority: Blocker
>              Labels: pull-request-available, test-stability
>
> Wordcount on Docker test (custom fs plugin) fails on Travis. 
> [https://travis-ci.org/KarmaGYZ/flink/builds/653829954]
> {code:bash}
> pass WordCount
> Checking for errors...
> Found error in log files:
> Attaching to docker_job-cluster_1
> job-cluster_1  | Starting the job-cluster
> job-cluster_1  | Starting standalonejob as a console application on host 
> 042c3c490edc.
> job-cluster_1  | ERROR StatusLogger No Log4j 2 configuration file found. 
> Using default configuration (logging only errors to the console), or user 
> programmatically provided configurations. Set system property 'log4j2.debug' 
> to show Log4j 2 internal initialization logging. See 
> https://logging.apache.org/log4j/2.x/manual/configuration.html for 
> instructions on how to configure Log4j 2
> Attaching to docker_taskmanager_1
> taskmanager_1  | Starting the task-manager
> taskmanager_1  | Starting taskexecutor as a console application on host 
> 059bd37e4232.
> taskmanager_1  | ERROR StatusLogger No Log4j 2 configuration file found. 
> Using default configuration (logging only errors to the console), or user 
> programmatically provided configurations. Set system property 'log4j2.debug' 
> to show Log4j 2 internal initialization logging. See 
> https://logging.apache.org/log4j/2.x/manual/configuration.html for 
> instructions on how to configure Log4j 2
> Checking for exceptions...
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to