flink-issues 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] (FLINK-10603) Reduce kafka test duration
Date Thu, 25 Oct 2018 08:39:00 GMT

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

ASF GitHub Bot commented on FLINK-10603:

yanghua commented on issue #6890: [FLINK-10603] Reduce kafka test duration
URL: https://github.com/apache/flink/pull/6890#issuecomment-432964247
   @zentol I think you misunderstood what I meant. I just used the exclusion method to locate
which test cases (compared to 0.9) took up too long test time. Because each kafka connector
has different test cases, we need to find out if the different test cases cost unreasonable
test time. Ultimately, these excluded test cases will definitely be restored. This of course
will not be my solution to reduce the test time.
   Because the 0.11 version is mainly implemented by @pnowojski , and more producer transaction
tests have been added since this version, I hope that he will evaluate it and whether it is
reasonable to spend these time.

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> Reduce kafka test duration
> --------------------------
>                 Key: FLINK-10603
>                 URL: https://issues.apache.org/jira/browse/FLINK-10603
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Kafka Connector, Tests
>    Affects Versions: 1.7.0
>            Reporter: Chesnay Schepler
>            Assignee: vinoyang
>            Priority: Major
>              Labels: pull-request-available
> The tests for the modern kafka connector take more than 10 minutes which is simply unacceptable.

This message was sent by Atlassian JIRA

View raw message