[GitHub] [flink] flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG

2019-10-24 Thread GitBox
flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate 
MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG
URL: https://github.com/apache/flink/pull/9900#issuecomment-542026880
 
 
   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 52978d1cecdc4e36718aa88eb2ca7649a0e03032 (Thu Oct 24 
18:02:04 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:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [flink] flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG

2019-10-18 Thread GitBox
flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate 
MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG
URL: https://github.com/apache/flink/pull/9900#issuecomment-542033352
 
 
   
   ## CI report:
   
   * a69bbc4f6eb0eac5509a989ebd5a4f31d8b028d6 : FAILURE 
[Build](https://travis-ci.com/flink-ci/flink/builds/131903595)
   * 5eb806c243fbb954ab1fc3386bb94721a52a6018 : SUCCESS 
[Build](https://travis-ci.com/flink-ci/flink/builds/132364278)
   * cfe3e5a530afff6c647cc26c7a13f2b1d745dadc : FAILURE 
[Build](https://travis-ci.com/flink-ci/flink/builds/132499394)
   * 52978d1cecdc4e36718aa88eb2ca7649a0e03032 : FAILURE 
[Build](https://travis-ci.com/flink-ci/flink/builds/132546768)
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
   


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:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [flink] flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG

2019-10-18 Thread GitBox
flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate 
MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG
URL: https://github.com/apache/flink/pull/9900#issuecomment-542026880
 
 
   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 52978d1cecdc4e36718aa88eb2ca7649a0e03032 (Fri Oct 18 
15:37:56 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:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [flink] flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG

2019-10-18 Thread GitBox
flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate 
MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG
URL: https://github.com/apache/flink/pull/9900#issuecomment-542033352
 
 
   
   ## CI report:
   
   * a69bbc4f6eb0eac5509a989ebd5a4f31d8b028d6 : FAILURE 
[Build](https://travis-ci.com/flink-ci/flink/builds/131903595)
   * 5eb806c243fbb954ab1fc3386bb94721a52a6018 : SUCCESS 
[Build](https://travis-ci.com/flink-ci/flink/builds/132364278)
   * cfe3e5a530afff6c647cc26c7a13f2b1d745dadc : FAILURE 
[Build](https://travis-ci.com/flink-ci/flink/builds/132499394)
   * 52978d1cecdc4e36718aa88eb2ca7649a0e03032 : PENDING 
[Build](https://travis-ci.com/flink-ci/flink/builds/132546768)
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
   


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:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [flink] flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG

2019-10-18 Thread GitBox
flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate 
MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG
URL: https://github.com/apache/flink/pull/9900#issuecomment-542026880
 
 
   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 52978d1cecdc4e36718aa88eb2ca7649a0e03032 (Fri Oct 18 
14:51:06 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:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [flink] flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG

2019-10-18 Thread GitBox
flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate 
MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG
URL: https://github.com/apache/flink/pull/9900#issuecomment-542033352
 
 
   
   ## CI report:
   
   * a69bbc4f6eb0eac5509a989ebd5a4f31d8b028d6 : FAILURE 
[Build](https://travis-ci.com/flink-ci/flink/builds/131903595)
   * 5eb806c243fbb954ab1fc3386bb94721a52a6018 : SUCCESS 
[Build](https://travis-ci.com/flink-ci/flink/builds/132364278)
   * cfe3e5a530afff6c647cc26c7a13f2b1d745dadc : FAILURE 
[Build](https://travis-ci.com/flink-ci/flink/builds/132499394)
   * 52978d1cecdc4e36718aa88eb2ca7649a0e03032 : UNKNOWN
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
   


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:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [flink] flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG

2019-10-18 Thread GitBox
flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate 
MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG
URL: https://github.com/apache/flink/pull/9900#issuecomment-542026880
 
 
   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 cfe3e5a530afff6c647cc26c7a13f2b1d745dadc (Fri Oct 18 
13:55:04 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:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [flink] flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG

2019-10-18 Thread GitBox
flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate 
MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG
URL: https://github.com/apache/flink/pull/9900#issuecomment-542026880
 
 
   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 cfe3e5a530afff6c647cc26c7a13f2b1d745dadc (Fri Oct 18 
13:32:42 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:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [flink] flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG

2019-10-18 Thread GitBox
flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate 
MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG
URL: https://github.com/apache/flink/pull/9900#issuecomment-542026880
 
 
   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 cfe3e5a530afff6c647cc26c7a13f2b1d745dadc (Fri Oct 18 
10:34:28 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:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [flink] flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG

2019-10-18 Thread GitBox
flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate 
MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG
URL: https://github.com/apache/flink/pull/9900#issuecomment-542033352
 
 
   
   ## CI report:
   
   * a69bbc4f6eb0eac5509a989ebd5a4f31d8b028d6 : FAILURE 
[Build](https://travis-ci.com/flink-ci/flink/builds/131903595)
   * 5eb806c243fbb954ab1fc3386bb94721a52a6018 : SUCCESS 
[Build](https://travis-ci.com/flink-ci/flink/builds/132364278)
   * cfe3e5a530afff6c647cc26c7a13f2b1d745dadc : FAILURE 
[Build](https://travis-ci.com/flink-ci/flink/builds/132499394)
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
   


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:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [flink] flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG

2019-10-18 Thread GitBox
flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate 
MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG
URL: https://github.com/apache/flink/pull/9900#issuecomment-542033352
 
 
   
   ## CI report:
   
   * a69bbc4f6eb0eac5509a989ebd5a4f31d8b028d6 : FAILURE 
[Build](https://travis-ci.com/flink-ci/flink/builds/131903595)
   * 5eb806c243fbb954ab1fc3386bb94721a52a6018 : SUCCESS 
[Build](https://travis-ci.com/flink-ci/flink/builds/132364278)
   * cfe3e5a530afff6c647cc26c7a13f2b1d745dadc : PENDING 
[Build](https://travis-ci.com/flink-ci/flink/builds/132499394)
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
   


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:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [flink] flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG

2019-10-18 Thread GitBox
flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate 
MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG
URL: https://github.com/apache/flink/pull/9900#issuecomment-542033352
 
 
   
   ## CI report:
   
   * a69bbc4f6eb0eac5509a989ebd5a4f31d8b028d6 : FAILURE 
[Build](https://travis-ci.com/flink-ci/flink/builds/131903595)
   * 5eb806c243fbb954ab1fc3386bb94721a52a6018 : SUCCESS 
[Build](https://travis-ci.com/flink-ci/flink/builds/132364278)
   * cfe3e5a530afff6c647cc26c7a13f2b1d745dadc : UNKNOWN
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
   


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:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [flink] flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG

2019-10-17 Thread GitBox
flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate 
MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG
URL: https://github.com/apache/flink/pull/9900#issuecomment-542033352
 
 
   
   ## CI report:
   
   * a69bbc4f6eb0eac5509a989ebd5a4f31d8b028d6 : FAILURE 
[Build](https://travis-ci.com/flink-ci/flink/builds/131903595)
   * 5eb806c243fbb954ab1fc3386bb94721a52a6018 : SUCCESS 
[Build](https://travis-ci.com/flink-ci/flink/builds/132364278)
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
   


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:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [flink] flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG

2019-10-17 Thread GitBox
flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate 
MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG
URL: https://github.com/apache/flink/pull/9900#issuecomment-542026880
 
 
   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 5eb806c243fbb954ab1fc3386bb94721a52a6018 (Thu Oct 17 
16:39:24 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:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [flink] flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG

2019-10-17 Thread GitBox
flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate 
MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG
URL: https://github.com/apache/flink/pull/9900#issuecomment-542033352
 
 
   
   ## CI report:
   
   * a69bbc4f6eb0eac5509a989ebd5a4f31d8b028d6 : FAILURE 
[Build](https://travis-ci.com/flink-ci/flink/builds/131903595)
   * 5eb806c243fbb954ab1fc3386bb94721a52a6018 : PENDING 
[Build](https://travis-ci.com/flink-ci/flink/builds/132364278)
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
   


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:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [flink] flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG

2019-10-17 Thread GitBox
flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate 
MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG
URL: https://github.com/apache/flink/pull/9900#issuecomment-542033352
 
 
   
   ## CI report:
   
   * a69bbc4f6eb0eac5509a989ebd5a4f31d8b028d6 : FAILURE 
[Build](https://travis-ci.com/flink-ci/flink/builds/131903595)
   * 5eb806c243fbb954ab1fc3386bb94721a52a6018 : UNKNOWN
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
   


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:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [flink] flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG

2019-10-17 Thread GitBox
flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate 
MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG
URL: https://github.com/apache/flink/pull/9900#issuecomment-542026880
 
 
   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 5eb806c243fbb954ab1fc3386bb94721a52a6018 (Thu Oct 17 
14:50:22 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:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [flink] flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG

2019-10-16 Thread GitBox
flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate 
MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG
URL: https://github.com/apache/flink/pull/9900#issuecomment-542033352
 
 
   
   ## CI report:
   
   * a69bbc4f6eb0eac5509a989ebd5a4f31d8b028d6 : FAILURE 
[Build](https://travis-ci.com/flink-ci/flink/builds/131903595)
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
   


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:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [flink] flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG

2019-10-16 Thread GitBox
flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate 
MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG
URL: https://github.com/apache/flink/pull/9900#issuecomment-542033352
 
 
   
   ## CI report:
   
   * a69bbc4f6eb0eac5509a989ebd5a4f31d8b028d6 : PENDING 
[Build](https://travis-ci.com/flink-ci/flink/builds/131903595)
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
   


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:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [flink] flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG

2019-10-16 Thread GitBox
flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate 
MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG
URL: https://github.com/apache/flink/pull/9900#issuecomment-542026880
 
 
   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 a69bbc4f6eb0eac5509a989ebd5a4f31d8b028d6 (Thu Oct 17 
04:23:54 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:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [flink] flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG

2019-10-16 Thread GitBox
flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate 
MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG
URL: https://github.com/apache/flink/pull/9900#issuecomment-542033352
 
 
   
   ## CI report:
   
   * a69bbc4f6eb0eac5509a989ebd5a4f31d8b028d6 : FAILURE 
[Build](https://travis-ci.com/flink-ci/flink/builds/131903595)
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
   


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:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [flink] flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG

2019-10-16 Thread GitBox
flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate 
MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG
URL: https://github.com/apache/flink/pull/9900#issuecomment-542033352
 
 
   
   ## CI report:
   
   * a69bbc4f6eb0eac5509a989ebd5a4f31d8b028d6 : PENDING 
[Build](https://travis-ci.com/flink-ci/flink/builds/131903595)
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
   


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:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [flink] flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG

2019-10-16 Thread GitBox
flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate 
MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG
URL: https://github.com/apache/flink/pull/9900#issuecomment-542026880
 
 
   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 a69bbc4f6eb0eac5509a989ebd5a4f31d8b028d6 (Thu Oct 17 
02:24:54 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:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [flink] flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG

2019-10-16 Thread GitBox
flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate 
MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG
URL: https://github.com/apache/flink/pull/9900#issuecomment-542026880
 
 
   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 a69bbc4f6eb0eac5509a989ebd5a4f31d8b028d6 (Wed Oct 16 
08:44:50 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:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [flink] flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG

2019-10-15 Thread GitBox
flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate 
MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG
URL: https://github.com/apache/flink/pull/9900#issuecomment-542033352
 
 
   
   ## CI report:
   
   * a69bbc4f6eb0eac5509a989ebd5a4f31d8b028d6 : FAILURE 
[Build](https://travis-ci.com/flink-ci/flink/builds/131903595)
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
   


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:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [flink] flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG

2019-10-15 Thread GitBox
flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate 
MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG
URL: https://github.com/apache/flink/pull/9900#issuecomment-542033352
 
 
   
   ## CI report:
   
   * a69bbc4f6eb0eac5509a989ebd5a4f31d8b028d6 : PENDING 
[Build](https://travis-ci.com/flink-ci/flink/builds/131903595)
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
   


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:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [flink] flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG

2019-10-14 Thread GitBox
flinkbot edited a comment on issue #9900: [FLINK-14366][tests] Annotate 
MiniCluster tests in flink-tests with AlsoRunWithSchedulerNG
URL: https://github.com/apache/flink/pull/9900#issuecomment-542033352
 
 
   
   ## CI report:
   
   * a69bbc4f6eb0eac5509a989ebd5a4f31d8b028d6 : FAILURE 
[Build](https://travis-ci.com/flink-ci/flink/builds/131903595)
   
   
   Bot commands
 The @flinkbot bot supports the following commands:
   
- `@flinkbot run travis` re-run the last Travis build
   


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:
us...@infra.apache.org


With regards,
Apache Git Services