Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FLINK-12370][python][travis] Integrated Travis for Python Table API. #8392

Closed
wants to merge 7 commits into from

Conversation

WeiZhong94
Copy link
Contributor

What is the purpose of the change

This pull request integrates travis for Python Table API.

Brief change log

  • Add new stage option in travis_controller.sh to enable python tests
  • Adjust minimizeCachedFiles logic to reserve files under flink-dist directory and test jars.

Verifying this change

This change is a trivial rework / code cleanup without any test coverage.

Does this pull request potentially affect one of the following parts:

  • Dependencies (does it add or upgrade a dependency): (no)
  • The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
  • The serializers: (no)
  • The runtime per-record code paths (performance sensitive): (no)
  • Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
  • The S3 file system connector: (no)

Documentation

  • Does this pull request introduce a new feature? (no)

@flinkbot
Copy link
Collaborator

flinkbot commented May 10, 2019

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.

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 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

Copy link
Contributor

@dianfu dianfu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@WeiZhong94 Thanks a lot for the PR. Have left a few comments.

@@ -23,6 +23,7 @@ STAGE_LIBRARIES="libraries"
STAGE_CONNECTORS="connectors"
STAGE_TESTS="tests"
STAGE_MISC="misc"
STAGE_PYTHON="python"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Put this line under STAGE_CORE="core" to keep the order same in .travis.yml

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

# limitations under the License.
################################################################################

HERE="`dirname \"$0\"`" # relative
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Most of the scripts of this file is same as travis_mvn_watchdog.sh. The only difference is how to execute the tests. What about moving the changes here to travis_mvn_watchdog.sh and do some refactoring of travis_mvn_watchdog.sh to make it work for both java and python? Maybe we should also rename travis_mvn_watchdog.sh to travis_watchdog.sh?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That makes sense. I have combined them in the new commit.

@WeiZhong94
Copy link
Contributor Author

@dianfu Thanks for your review! I have addressed your comments.

Copy link
Contributor

@dianfu dianfu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@WeiZhong94 Thanks a lot for the update. The new PR LGTM. Have left just one minor comments.

@@ -78,6 +83,24 @@ UPLOAD_SECRET_KEY=$ARTIFACTS_AWS_SECRET_KEY

ARTIFACTS_FILE=${TRAVIS_JOB_NUMBER}.tar.gz

if [ $TEST == $STAGE_PYTHON ]; then

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove the empty line

Copy link
Member

@sunjincheng121 sunjincheng121 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR. @WeiZhong94
LGTM. +1 to merged.
Best,Jincheng

@sunjincheng121
Copy link
Member

I find one thing we need double check, is the cost of the testing, maybe there is a bug need fix(I am not sure, I will check it):
image
@WeiZhong94

@sunjincheng121
Copy link
Member

We have two options for Python integration with Travis.

  1. It is the addition of a python stage that PR currently reflects. Instead of using MVN for testing, it runs a separate shell.
  2. Using MVN to execute the shell, Python validation is also MVN is tested. I personally prefer the current PR program. The reason is that:
    • The Python API is a different language from Java/Scala. The code management and testing methods are not dependent on MVN. Python multi-version and Python API functional tests are combined using Conda and Tox. So we choose not to use the MVN solution;

    • The Python API is a new language API that has just been incorporated into Flink. We would like to have an intuitive understanding of Python's details in the Travis process and intuitively observe the time spent testing the Python API. So choose a separate stage and a separate run output solution.

Of course, there are 2 aspects, 1. Independent stage 2. Is it integrated into MVN, that is, 2x2=4 options, I tend to the current PR.

What do you think? @aljoscha @zentol

@sunjincheng121
Copy link
Member

I find one thing we need double check, is the cost of the testing, maybe there is a bug need fix(I am not sure, I will check it):
image
@WeiZhong94

the script bug, see follows:
image

@WeiZhong94
Copy link
Contributor Author

@sunjincheng121 Thanks for your review! Sorry for these mistakes. I have fixed them in the new commit and ensure the travis works correctly.

@sunjincheng121
Copy link
Member

Thanks for the fix @WeiZhong94
LGTM. +1 to merged
@flinkbot approve all

sunjincheng121 pushed a commit to sunjincheng121/flink that referenced this pull request May 15, 2019
Brief change log:
 - Added python stage for Python API travis testing.
 - Integrated flink-python/dev/lint-python.sh for CI testing of the Python API.

This closes apache#8392
@asfgit asfgit closed this in d95d395 May 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants