-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Use wheels for Dataflow postcommit tests #25970
Conversation
Codecov Report
@@ Coverage Diff @@
## master #25970 +/- ##
==========================================
- Coverage 71.17% 71.17% -0.01%
==========================================
Files 787 787
Lines 103294 103311 +17
==========================================
+ Hits 73523 73532 +9
- Misses 28283 28291 +8
Partials 1488 1488
Flags with carried forward coverage won't be shown. Click here to find out more. see 8 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
53f64a9
to
e50b97e
Compare
008170e
to
2a4e5a3
Compare
fff0bf3
to
e783586
Compare
Tests on dataflow actually passed and indeed takes much faster: https://ci-beam.apache.org/job/beam_PostCommit_Python310_PR/38/ However, flink runner test not running due to -- this is due to pypa/setuptools#1222 |
Run Python 3.7 PostCommit |
Run Python 3.8 PostCommit |
Run Python 3.9 PostCommit |
|
Run Python 3.8 PostCommit |
Run Python 3.10 PostCommit |
Thanks @tvalentyn for the suggestion. I have rewritten the part of build wheel. Summary of change since last review:
PostCommit succeeded. Ready for review again. |
gradle.properties
Outdated
flink_versions=1.12,1.13,1.14,1.15,1.16 | ||
# supported python versions | ||
python_versions=3.7,3.8,3.9,3.10 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a gradle property here because now :sdks:python
project need it to define bdist tasks. This also simplifies gradle.properties in python/test-suites a little bit because now it has a single source of truth for supported python version
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we use this one instead?
final static List<String> ALL_SUPPORTED_VERSIONS = [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for pointing to this. Not aware of it. This code path is for Jenkins only (.test-infra/jenkins/
); gradle files works independently with Jenkins (gradle tasks can trigger locally). To reduce to duplicate declaration, refer to gradle.properties
in Jenkins script should work
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there is also https://github.com/apache/beam/blob/master/sdks/python/test-suites/gradle.properties Would be good to see if we can these version configurations together.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is https://github.com/apache/beam/blob/master/sdks/python/test-suites/gradle.properties accessible from the context where you need this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The problem is sdks/python/test-suites/gradle.properties
is not accessible to sdks/python
gradle project. I understand test-suites/gradle.properties
as a configuration to manage which python version used in different test. While for bdist it belongs to the python root project (just as sdist). I did not find a source of truth for supported Python versions accessible in the sdks/python
context.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ack, thanks for checking. @AnandInguva FYI one more place to add python versions in the future.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, will experiment to read gradle.properties in jenkins/github actions so reduce the duplicate declarations of py version
sdks/python/build.gradle
Outdated
environment CIBW_BUILD: "cp${pyversion}-${idsuffix}" | ||
environment CIBW_ENVIRONMENT: "SETUPTOOLS_USE_DISTUTILS=stdlib" | ||
environment CIBW_BEFORE_BUILD: "pip install cython numpy && pip install --upgrade setuptools" | ||
// note: sync cibuildwheel version with GitHub Action build_wheel |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lets add a pointer to exact place where this needs to be modified and maybe make it a inline comment, and do the same in the counterpart where wheels are built.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks, added to both build.gradle and .yml
Doing a rebase, will squash the reviewed commit (that is before 8329ee5) |
Reminder about code freeze: https://lists.apache.org/thread/rpmq9r9tbgrry8yco70mzyt4psyk5m20 |
Thank you very much, @Abacn ! |
Run Python 3.7 PostCommit |
Run Python 3.11 PostCommit |
Jenkins not triggering. The latest commit just switched to opt-in buildWheels from opt-out (convenient for testing without the need of triggering seed job). Merging based on the signal in 697635a. at there Python postcommit passed. "pending" tests were actually passed; failed Java tests irrelevant. |
There are 3 stuck Java test and 1 failed java tests unrelated. Other precommits passed. Merging for now. |
Fixes #25966
Fixes #26049
Please add a meaningful description for your change here
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
addresses #123
), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, commentfixes #<ISSUE NUMBER>
instead.CHANGES.md
with noteworthy changes.See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)
See CI.md for more information about GitHub Actions CI.