-
Notifications
You must be signed in to change notification settings - Fork 4.5k
GA Migration Java PostCommit ValidatesRunner (Flink, Flink Jv11, Samza, Twister2) #23267
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
Conversation
e954381 to
1cd3ab3
Compare
|
Assigning reviewers. If you would like to opt out of this review, comment R: @Abacn for label build. Available commands:
The PR bot will only process comments in the main thread (not review comments). |
|
Reminder, please take a look at this pr: @Abacn |
.github/workflows/job-postcommit-java-validatesrunner-flink-java11.yml
Outdated
Show resolved
Hide resolved
.github/workflows/job-postcommit-java-validatesrunner-flink-java11.yml
Outdated
Show resolved
Hide resolved
|
Reminder, please take a look at this pr: @Abacn |
| fail-fast: false | ||
| matrix: | ||
| flink-versions: ${{fromJson(needs.set-properties.outputs.properties).JavaTestProperties.FLINK_VERSIONS}} | ||
| exclude: # exclude other versions, we only need 1.13 for this test |
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.
We should do the same thing as in the other test if we only need 1.13 (use that as the version instead of an exclude list)
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.
I recently bumped DataProc to 2.1 which runs flink 1.15. DataProc never supports flink 1.13 (Dataproc 2.0 runs flink 1.12)
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.
@Abacn should we just be pinning to 1.15 across both suites? Probably?
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.
yeah I would suggest. For Jenkins it is set here:
| static String getFlinkVersion() { |
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.
Hi @damccorm
So for this workflow, should I use the 1.15 flink version instead of 1.13?
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.
Yeah - could you actually set a FLINK_LATEST property to 1.15 here - https://github.com/apache/beam/blob/9b3b403ae9c071dcef0e801c892eab2203db88df/.github/actions/setup-default-test-properties/test-properties.json#LL17C48-L17C48 - and use that in both workflows?
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.
Yeah I can apply the change, just I tested using 1.15 but the test failed, I changed back to 1.13 and the test passed. 🤔
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.
@Abacn any ideas? https://github.com/MarcoRob/beam/actions/runs/3622938989/jobs/6108239170
I recently bumped DataProc to 2.1 which runs flink 1.15. DataProc never supports flink 1.13 (Dataproc 2.0 runs flink 1.12)
Does this actually affect this set of tests? Or are these just running on a local cluster? My guess is that its all local
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.
No, that change does not affect local clusters. Running flink 1.13 on local cluster does not involve DataProc and does not have problem. For test failure not sure the cause, but we can defer the version aligning as future task if bumping version breaks test.
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.
Change applied using Flink Version 1.13, I applied the following property as FLINK_DEFAULT_VERSION
Codecov Report
@@ Coverage Diff @@
## master #23267 +/- ##
==========================================
- Coverage 73.40% 73.37% -0.03%
==========================================
Files 718 719 +1
Lines 95652 97206 +1554
==========================================
+ Hits 70211 71323 +1112
- Misses 24130 24536 +406
- Partials 1311 1347 +36
Flags with carried forward coverage won't be shown. Click here to find out more.
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
|
This pull request has been marked as stale due to 60 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that’s incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the dev@beam.apache.org list. Thank you for your contributions. |
|
hmmm what should we do here @damccorm ? |
|
Lets leave this open for now so that we can take this effort forward if we're able to get the resources to do so. |
As part of the migration of Precommit and Postcommit Jobs from Jenkins to GA in self-hosted runners, this PR contains:
The migrated workflows were added to CI.md
DO NOT MERGE until the effort to use self-hosted runners is completed #22703
These workflows use base actions listed in #23109 (Dependency)
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
R: @username).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.