From issues-return-280426-apmail-flink-issues-archive=flink.apache.org@flink.apache.org Thu Oct 17 14:06:46 2019 Return-Path: X-Original-To: apmail-flink-issues-archive@minotaur.apache.org Delivered-To: apmail-flink-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by minotaur.apache.org (Postfix) with SMTP id 714CF19B5B for ; Thu, 17 Oct 2019 14:06:46 +0000 (UTC) Received: (qmail 32303 invoked by uid 500); 17 Oct 2019 14:06:34 -0000 Delivered-To: apmail-flink-issues-archive@flink.apache.org Received: (qmail 32265 invoked by uid 500); 17 Oct 2019 14:06:34 -0000 Mailing-List: contact issues-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flink.apache.org Delivered-To: mailing list issues@flink.apache.org Received: (qmail 32220 invoked by uid 99); 17 Oct 2019 14:06:34 -0000 Received: from ec2-52-202-80-70.compute-1.amazonaws.com (HELO gitbox.apache.org) (52.202.80.70) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Oct 2019 14:06:34 +0000 From: GitBox To: issues@flink.apache.org Subject: [GitHub] [flink] flinkbot edited a comment on issue #9912: [FLINK-14370][kafka][test-stability] Fix the cascading failure in kaProducerTestBase. Message-ID: <157132119439.844.12006358583610807627.gitbox@gitbox.apache.org> Date: Thu, 17 Oct 2019 14:06:34 -0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit flinkbot edited a comment on issue #9912: [FLINK-14370][kafka][test-stability] Fix the cascading failure in kaProducerTestBase. URL: https://github.com/apache/flink/pull/9912#issuecomment-542705661 Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community to review your pull request. We will use this comment to track the progress of the review. ## Automated Checks Last check on commit d3faff4e2b44b01a43d3716ad2eb1f4cd2c4b054 (Thu Oct 17 14:06:33 UTC 2019) **Warnings:** * No documentation files were touched! Remember to keep the Flink docs up to date! Mention the bot in a comment to re-run the automated checks. ## Review Progress * ❓ 1. The [description] looks good. * ❓ 2. There is [consensus] that the contribution should go into to Flink. * ❓ 3. Needs [attention] from. * ❓ 4. The change fits into the overall [architecture]. * ❓ 5. Overall code [quality] is good. Please see the [Pull Request Review Guide](https://flink.apache.org/contributing/reviewing-prs.html) for a full explanation of the review process.
The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commands The @flinkbot bot supports the following commands: - `@flinkbot approve description` to approve one or more aspects (aspects: `description`, `consensus`, `architecture` and `quality`) - `@flinkbot approve all` to approve all aspects - `@flinkbot approve-until architecture` to approve everything until `architecture` - `@flinkbot attention @username1 [@username2 ..]` to require somebody's attention - `@flinkbot disapprove architecture` to remove an approval you gave earlier
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: users@infra.apache.org With regards, Apache Git Services