[GitHub] [flink] flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server
flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server URL: https://github.com/apache/flink/pull/9759#issuecomment-534556628 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 64c714562b10cf23732b6bedb05f272634181e47 (Thu Oct 24 18:05:34 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 #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server
flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server URL: https://github.com/apache/flink/pull/9759#issuecomment-534565511 ## CI report: * 70cf88200f1b09ca6932462f4d51834c339077e3 : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/128921710) * 9fe76d41aa12a997006d5e05c487d9d1621dbeff : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/129089756) * 442e396d83612a1835f1c29b511946d9f35d6294 : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/129240079) * d913d3696819402493a830a96b650bcea66a6f09 : CANCELED [Build](https://travis-ci.com/flink-ci/flink/builds/132308198) * b9d1055a38764f218a4cead4a17e3c772637f3f1 : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/132312033) * 64c714562b10cf23732b6bedb05f272634181e47 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/132857809) 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 #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server
flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server URL: https://github.com/apache/flink/pull/9759#issuecomment-534565511 ## CI report: * 70cf88200f1b09ca6932462f4d51834c339077e3 : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/128921710) * 9fe76d41aa12a997006d5e05c487d9d1621dbeff : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/129089756) * 442e396d83612a1835f1c29b511946d9f35d6294 : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/129240079) * d913d3696819402493a830a96b650bcea66a6f09 : CANCELED [Build](https://travis-ci.com/flink-ci/flink/builds/132308198) * b9d1055a38764f218a4cead4a17e3c772637f3f1 : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/132312033) * 64c714562b10cf23732b6bedb05f272634181e47 : PENDING [Build](https://travis-ci.com/flink-ci/flink/builds/132857809) 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 #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server
flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server URL: https://github.com/apache/flink/pull/9759#issuecomment-534565511 ## CI report: * 70cf88200f1b09ca6932462f4d51834c339077e3 : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/128921710) * 9fe76d41aa12a997006d5e05c487d9d1621dbeff : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/129089756) * 442e396d83612a1835f1c29b511946d9f35d6294 : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/129240079) * d913d3696819402493a830a96b650bcea66a6f09 : CANCELED [Build](https://travis-ci.com/flink-ci/flink/builds/132308198) * b9d1055a38764f218a4cead4a17e3c772637f3f1 : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/132312033) * 64c714562b10cf23732b6bedb05f272634181e47 : 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 #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server
flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server URL: https://github.com/apache/flink/pull/9759#issuecomment-534556628 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 64c714562b10cf23732b6bedb05f272634181e47 (Mon Oct 21 16:15:51 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 #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server
flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server URL: https://github.com/apache/flink/pull/9759#issuecomment-534556628 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 64c714562b10cf23732b6bedb05f272634181e47 (Mon Oct 21 16:13:49 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 #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server
flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server URL: https://github.com/apache/flink/pull/9759#issuecomment-534556628 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 64c714562b10cf23732b6bedb05f272634181e47 (Mon Oct 21 16:11:46 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 #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server
flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server URL: https://github.com/apache/flink/pull/9759#issuecomment-534556628 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 64c714562b10cf23732b6bedb05f272634181e47 (Mon Oct 21 16:09:44 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 #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server
flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server URL: https://github.com/apache/flink/pull/9759#issuecomment-534556628 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 64c714562b10cf23732b6bedb05f272634181e47 (Mon Oct 21 16:08:43 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 #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server
flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server URL: https://github.com/apache/flink/pull/9759#issuecomment-534556628 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 64c714562b10cf23732b6bedb05f272634181e47 (Mon Oct 21 16:06:40 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 #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server
flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server URL: https://github.com/apache/flink/pull/9759#issuecomment-534556628 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 64c714562b10cf23732b6bedb05f272634181e47 (Mon Oct 21 16:05:44 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 #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server
flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server URL: https://github.com/apache/flink/pull/9759#issuecomment-534556628 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 64c714562b10cf23732b6bedb05f272634181e47 (Mon Oct 21 16:04:38 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 #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server
flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server URL: https://github.com/apache/flink/pull/9759#issuecomment-534556628 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 64c714562b10cf23732b6bedb05f272634181e47 (Mon Oct 21 16:03:37 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 #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server
flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server URL: https://github.com/apache/flink/pull/9759#issuecomment-534556628 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 b9d1055a38764f218a4cead4a17e3c772637f3f1 (Fri Oct 18 15:28:45 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 #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server
flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server URL: https://github.com/apache/flink/pull/9759#issuecomment-534556628 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 b9d1055a38764f218a4cead4a17e3c772637f3f1 (Thu Oct 17 14:57:29 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 #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server
flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server URL: https://github.com/apache/flink/pull/9759#issuecomment-534565511 ## CI report: * 70cf88200f1b09ca6932462f4d51834c339077e3 : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/128921710) * 9fe76d41aa12a997006d5e05c487d9d1621dbeff : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/129089756) * 442e396d83612a1835f1c29b511946d9f35d6294 : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/129240079) * d913d3696819402493a830a96b650bcea66a6f09 : CANCELED [Build](https://travis-ci.com/flink-ci/flink/builds/132308198) * b9d1055a38764f218a4cead4a17e3c772637f3f1 : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/132312033) 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 #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server
flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server URL: https://github.com/apache/flink/pull/9759#issuecomment-534565511 ## CI report: * 70cf88200f1b09ca6932462f4d51834c339077e3 : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/128921710) * 9fe76d41aa12a997006d5e05c487d9d1621dbeff : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/129089756) * 442e396d83612a1835f1c29b511946d9f35d6294 : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/129240079) * d913d3696819402493a830a96b650bcea66a6f09 : CANCELED [Build](https://travis-ci.com/flink-ci/flink/builds/132308198) * b9d1055a38764f218a4cead4a17e3c772637f3f1 : PENDING [Build](https://travis-ci.com/flink-ci/flink/builds/132312033) 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 #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server
flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server URL: https://github.com/apache/flink/pull/9759#issuecomment-534565511 ## CI report: * 70cf88200f1b09ca6932462f4d51834c339077e3 : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/128921710) * 9fe76d41aa12a997006d5e05c487d9d1621dbeff : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/129089756) * 442e396d83612a1835f1c29b511946d9f35d6294 : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/129240079) * d913d3696819402493a830a96b650bcea66a6f09 : PENDING [Build](https://travis-ci.com/flink-ci/flink/builds/132308198) * b9d1055a38764f218a4cead4a17e3c772637f3f1 : 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 #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server
flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server URL: https://github.com/apache/flink/pull/9759#issuecomment-534556628 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 b9d1055a38764f218a4cead4a17e3c772637f3f1 (Thu Oct 17 10:18:14 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 #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server
flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server URL: https://github.com/apache/flink/pull/9759#issuecomment-534556628 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 b9d1055a38764f218a4cead4a17e3c772637f3f1 (Thu Oct 17 10:16:12 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 #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server
flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server URL: https://github.com/apache/flink/pull/9759#issuecomment-534565511 ## CI report: * 70cf88200f1b09ca6932462f4d51834c339077e3 : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/128921710) * 9fe76d41aa12a997006d5e05c487d9d1621dbeff : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/129089756) * 442e396d83612a1835f1c29b511946d9f35d6294 : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/129240079) * d913d3696819402493a830a96b650bcea66a6f09 : 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 #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server
flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server URL: https://github.com/apache/flink/pull/9759#issuecomment-534556628 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 d913d3696819402493a830a96b650bcea66a6f09 (Thu Oct 17 09:39:31 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 #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server
flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server URL: https://github.com/apache/flink/pull/9759#issuecomment-534556628 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 442e396d83612a1835f1c29b511946d9f35d6294 (Wed Oct 16 12:02:09 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 #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server
flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server URL: https://github.com/apache/flink/pull/9759#issuecomment-534556628 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 442e396d83612a1835f1c29b511946d9f35d6294 (Wed Oct 16 10:33:40 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 #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server
flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server URL: https://github.com/apache/flink/pull/9759#issuecomment-534556628 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 442e396d83612a1835f1c29b511946d9f35d6294 (Wed Oct 16 09:15:18 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 #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server
flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server URL: https://github.com/apache/flink/pull/9759#issuecomment-534556628 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 442e396d83612a1835f1c29b511946d9f35d6294 (Wed Oct 16 09:06:58 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 #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server
flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server URL: https://github.com/apache/flink/pull/9759#issuecomment-534565511 ## CI report: * 70cf88200f1b09ca6932462f4d51834c339077e3 : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/128921710) * 9fe76d41aa12a997006d5e05c487d9d1621dbeff : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/129089756) * 442e396d83612a1835f1c29b511946d9f35d6294 : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/129240079) 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 #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server
flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server URL: https://github.com/apache/flink/pull/9759#issuecomment-534565511 ## CI report: * 70cf88200f1b09ca6932462f4d51834c339077e3 : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/128921710) * 9fe76d41aa12a997006d5e05c487d9d1621dbeff : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/129089756) * 442e396d83612a1835f1c29b511946d9f35d6294 : PENDING [Build](https://travis-ci.com/flink-ci/flink/builds/129240079) 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 #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server
flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server URL: https://github.com/apache/flink/pull/9759#issuecomment-534565511 ## CI report: * 70cf88200f1b09ca6932462f4d51834c339077e3 : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/128921710) * 9fe76d41aa12a997006d5e05c487d9d1621dbeff : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/129089756) * 442e396d83612a1835f1c29b511946d9f35d6294 : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/129240079) 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 #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server
flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server URL: https://github.com/apache/flink/pull/9759#issuecomment-534565511 ## CI report: * 70cf88200f1b09ca6932462f4d51834c339077e3 : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/128921710) * 9fe76d41aa12a997006d5e05c487d9d1621dbeff : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/129089756) * 442e396d83612a1835f1c29b511946d9f35d6294 : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/129240079) 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 #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server
flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server URL: https://github.com/apache/flink/pull/9759#issuecomment-534565511 ## CI report: * 70cf88200f1b09ca6932462f4d51834c339077e3 : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/128921710) * 9fe76d41aa12a997006d5e05c487d9d1621dbeff : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/129089756) * 442e396d83612a1835f1c29b511946d9f35d6294 : PENDING [Build](https://travis-ci.com/flink-ci/flink/builds/129240079) 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 #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server
flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server URL: https://github.com/apache/flink/pull/9759#issuecomment-534565511 ## CI report: * 70cf88200f1b09ca6932462f4d51834c339077e3 : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/128921710) * 9fe76d41aa12a997006d5e05c487d9d1621dbeff : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/129089756) * 442e396d83612a1835f1c29b511946d9f35d6294 : UNKNOWN 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 #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server
flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server URL: https://github.com/apache/flink/pull/9759#issuecomment-534565511 ## CI report: * 70cf88200f1b09ca6932462f4d51834c339077e3 : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/128921710) * 9fe76d41aa12a997006d5e05c487d9d1621dbeff : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/129089756) 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 #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server
flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server URL: https://github.com/apache/flink/pull/9759#issuecomment-534565511 ## CI report: * 70cf88200f1b09ca6932462f4d51834c339077e3 : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/128921710) * 9fe76d41aa12a997006d5e05c487d9d1621dbeff : PENDING [Build](https://travis-ci.com/flink-ci/flink/builds/129089756) 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 #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server
flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server URL: https://github.com/apache/flink/pull/9759#issuecomment-534565511 ## CI report: * 70cf88200f1b09ca6932462f4d51834c339077e3 : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/128921710) * 9fe76d41aa12a997006d5e05c487d9d1621dbeff : UNKNOWN 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 #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server
flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server URL: https://github.com/apache/flink/pull/9759#issuecomment-534565511 ## CI report: * 70cf88200f1b09ca6932462f4d51834c339077e3 : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/128921710) 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 #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server
flinkbot edited a comment on issue #9759: [FLINK-14169][history-server] Cleanup expired jobs from history server URL: https://github.com/apache/flink/pull/9759#issuecomment-534565511 ## CI report: * 70cf88200f1b09ca6932462f4d51834c339077e3 : PENDING [Build](https://travis-ci.com/flink-ci/flink/builds/128921710) 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
