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

ASF GitHub Bot commented on FLINK-7297:
---------------------------------------

GitHub user zhangminglei opened a pull request:

    https://github.com/apache/flink/pull/4423

    [FLINK-7297] [table] Fix failed to run CorrelateITCase class under wi…

    With a environment on Windows, Test run failed as reference to 
UserDefinedFunctionTestUtils is ambiguous;
    it is imported twice in the same scope by ```import 
org.apache.flink.table.utils._``` and ```import 
org.apache.flink.table.runtime.utils._```
    
    Both happened on stream and batch package.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/zhangminglei/flink flink-7302-CorrelateITCase

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/4423.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #4423
    
----
commit e055062cd3a43c5ea297fa4206103b019831e9d1
Author: zhangminglei <[email protected]>
Date:   2017-07-31T10:01:13Z

    [FLINK-7297] [table] Fix failed to run CorrelateITCase class under windows 
environment

----


> Instable Kafka09ProducerITCase.testCustomPartitioning test case
> ---------------------------------------------------------------
>
>                 Key: FLINK-7297
>                 URL: https://issues.apache.org/jira/browse/FLINK-7297
>             Project: Flink
>          Issue Type: Bug
>          Components: Kafka Connector, Tests
>    Affects Versions: 1.4.0
>            Reporter: Till Rohrmann
>            Priority: Critical
>              Labels: test-stability
>
> There seems to be a test instability of 
> {{Kafka09ProducerITCase>KafkaProducerTestBase.testCustomPartitioning}} on 
> Travis.
> https://travis-ci.org/apache/flink/jobs/258538636



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to