[#28187] Add gradle targets to execute python tests with prism.#32637
[#28187] Add gradle targets to execute python tests with prism.#32637lostluck merged 3 commits intoapache:masterfrom
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #32637 +/- ##
=========================================
Coverage 58.84% 58.84%
Complexity 3091 3091
=========================================
Files 1130 1130
Lines 174044 174048 +4
Branches 3320 3312 -8
=========================================
+ Hits 102414 102422 +8
- Misses 68293 68295 +2
+ Partials 3337 3331 -6
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
|
Assigning reviewers. If you would like to opt out of this review, comment R: @shunping for label python. Available commands:
The PR bot will only process comments in the main thread (not review comments). |
shunping
left a comment
There was a problem hiding this comment.
LGTM! Are we going to trigger these validation tests in any github action?
|
@shunping yup! I just wanted that in a separate PR, as mentioned in the PR description. |
…apache#32637) * [apache#28187] Add gradle targets to execute python tests with prism. * Add issues for non-expansion service skipped tests. * Format diff. --------- Co-authored-by: lostluck <13907733+lostluck@users.noreply.github.com>
This is a required task before adding a Precommit action for running the Python suites against prism. That work will be in a separate PR.
A part of #28187.
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.mdwith 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 or the workflows README to see a list of phrases to trigger workflows.