You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2020/01/21 03:56:42 UTC
[GitHub] [flink] wangxiyuan opened a new pull request #10912: [hotfix][e2e]
Fix e2e test re-run error
wangxiyuan opened a new pull request #10912: [hotfix][e2e] Fix e2e test re-run error
URL: https://github.com/apache/flink/pull/10912
<!--
*Thank you very much for contributing to Apache Flink - we are happy that you want to help us improve Flink. To help the community review your contribution in the best possible way, please go through the checklist below, which will get the contribution into a shape in which it can be best reviewed.*
*Please understand that we do not do this to make contributions to Flink a hassle. In order to uphold a high standard of quality for code contributions, while at the same time managing a large number of contributions, we need contributors to prepare the contributions well, and give reviewers enough contextual information for the review. Please also understand that contributions that do not follow this guide will take longer to review and thus typically be picked up with lower priority by the community.*
## Contribution Checklist
- Make sure that the pull request corresponds to a [JIRA issue](https://issues.apache.org/jira/projects/FLINK/issues). Exceptions are made for typos in JavaDoc or documentation files, which need no JIRA issue.
- Name the pull request in the form "[FLINK-XXXX] [component] Title of the pull request", where *FLINK-XXXX* should be replaced by the actual issue number. Skip *component* if you are unsure about which is the best component.
Typo fixes that have no associated JIRA issue should be named following this pattern: `[hotfix] [docs] Fix typo in event time introduction` or `[hotfix] [javadocs] Expand JavaDoc for PuncuatedWatermarkGenerator`.
- Fill out the template below to describe the changes contributed by the pull request. That will give reviewers the context they need to do the review.
- Make sure that the change passes the automated tests, i.e., `mvn clean verify` passes. You can set up Travis CI to do that following [this guide](https://flink.apache.org/contributing/contribute-code.html#open-a-pull-request).
- Each pull request should address only one issue, not mix up code from multiple issues.
- Each commit in the pull request has a meaningful commit message (including the JIRA id)
- Once all items of the checklist are addressed, remove the above text and this checklist, leaving only the filled out template below.
**(The sections below can be removed for hotfixes of typos)**
-->
## What is the purpose of the change
If run Flink e2e test with a pre-built Flink like `./tools/travis/nightly.sh split_sticky.sh`, it will fail with the error:
```
[ERROR] [ERROR] Could not find the selected project in the reactor: flink-walkthroughs/flink-walkthrough-datastream-java/target/classes/archetype-resources @
[ERROR] Could not find the selected project in the reactor: flink-walkthroughs/flink-walkthrough-datastream-java/target/classes/archetype-resources -> [Help 1]
```
It because that the the target file for flink-walkthroughs contains pom.xml, then the e2e script treat them as modules. For example
```
flink-walkthroughs/flink-walkthrough-table-scala/target/classes/archetype-resources/pom.xml
```
## Brief change log
Reduce the search depth to avoid treat the target file as modules.
## Verifying this change
Just re-run the e2e script in a pre-built Flink folder.
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): (yes / **no**)
- The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (yes / **no**)
- The serializers: (yes / **no** / don't know)
- The runtime per-record code paths (performance sensitive): (yes / **no** / don't know)
- Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / **no** / don't know)
- The S3 file system connector: (yes / **no** / don't know)
## Documentation
- Does this pull request introduce a new feature? (yes / **no**)
- If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] zentol merged pull request #10912: [hotfix][e2e] Fix e2e
test re-run error
Posted by GitBox <gi...@apache.org>.
zentol merged pull request #10912: [hotfix][e2e] Fix e2e test re-run error
URL: https://github.com/apache/flink/pull/10912
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #10912: [hotfix][e2e]
Fix e2e test re-run error
Posted by GitBox <gi...@apache.org>.
flinkbot edited a comment on issue #10912: [hotfix][e2e] Fix e2e test re-run error
URL: https://github.com/apache/flink/pull/10912#issuecomment-576510935
<!--
Meta data
Hash:dd3583af0f1bf8dc98e044271c4a9209a99a8aac Status:SUCCESS URL:https://travis-ci.com/flink-ci/flink/builds/145306260 TriggerType:PUSH TriggerID:dd3583af0f1bf8dc98e044271c4a9209a99a8aac
Hash:dd3583af0f1bf8dc98e044271c4a9209a99a8aac Status:SUCCESS URL:https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4523 TriggerType:PUSH TriggerID:dd3583af0f1bf8dc98e044271c4a9209a99a8aac
-->
## CI report:
* dd3583af0f1bf8dc98e044271c4a9209a99a8aac Travis: [SUCCESS](https://travis-ci.com/flink-ci/flink/builds/145306260) Azure: [SUCCESS](https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4523)
<details>
<summary>Bot commands</summary>
The @flinkbot bot supports the following commands:
- `@flinkbot run travis` re-run the last Travis build
- `@flinkbot run azure` re-run the last Azure build
</details>
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #10912: [hotfix][e2e]
Fix e2e test re-run error
Posted by GitBox <gi...@apache.org>.
flinkbot edited a comment on issue #10912: [hotfix][e2e] Fix e2e test re-run error
URL: https://github.com/apache/flink/pull/10912#issuecomment-576510935
<!--
Meta data
Hash:dd3583af0f1bf8dc98e044271c4a9209a99a8aac Status:PENDING URL:https://travis-ci.com/flink-ci/flink/builds/145306260 TriggerType:PUSH TriggerID:dd3583af0f1bf8dc98e044271c4a9209a99a8aac
Hash:dd3583af0f1bf8dc98e044271c4a9209a99a8aac Status:PENDING URL:https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4523 TriggerType:PUSH TriggerID:dd3583af0f1bf8dc98e044271c4a9209a99a8aac
-->
## CI report:
* dd3583af0f1bf8dc98e044271c4a9209a99a8aac Travis: [PENDING](https://travis-ci.com/flink-ci/flink/builds/145306260) Azure: [PENDING](https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4523)
<details>
<summary>Bot commands</summary>
The @flinkbot bot supports the following commands:
- `@flinkbot run travis` re-run the last Travis build
- `@flinkbot run azure` re-run the last Azure build
</details>
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] flinkbot commented on issue #10912: [hotfix][e2e] Fix e2e
test re-run error
Posted by GitBox <gi...@apache.org>.
flinkbot commented on issue #10912: [hotfix][e2e] Fix e2e test re-run error
URL: https://github.com/apache/flink/pull/10912#issuecomment-576510935
<!--
Meta data
Hash:dd3583af0f1bf8dc98e044271c4a9209a99a8aac Status:UNKNOWN URL:TBD TriggerType:PUSH TriggerID:dd3583af0f1bf8dc98e044271c4a9209a99a8aac
-->
## CI report:
* dd3583af0f1bf8dc98e044271c4a9209a99a8aac UNKNOWN
<details>
<summary>Bot commands</summary>
The @flinkbot bot supports the following commands:
- `@flinkbot run travis` re-run the last Travis build
- `@flinkbot run azure` re-run the last Azure build
</details>
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] wangxiyuan commented on issue #10912: [hotfix][e2e] Fix e2e
test re-run error
Posted by GitBox <gi...@apache.org>.
wangxiyuan commented on issue #10912: [hotfix][e2e] Fix e2e test re-run error
URL: https://github.com/apache/flink/pull/10912#issuecomment-581192519
any committer can take a look?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] flinkbot commented on issue #10912: [hotfix][e2e] Fix e2e
test re-run error
Posted by GitBox <gi...@apache.org>.
flinkbot commented on issue #10912: [hotfix][e2e] Fix e2e test re-run error
URL: https://github.com/apache/flink/pull/10912#issuecomment-576508209
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 dd3583af0f1bf8dc98e044271c4a9209a99a8aac (Tue Jan 21 03:59:42 UTC 2020)
**Warnings:**
* No documentation files were touched! Remember to keep the Flink docs up to date!
<sub>Mention the bot in a comment to re-run the automated checks.</sub>
## 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.<details>
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 <summary>Bot commands</summary>
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
</details>
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services