-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
[BEAM-10955] Fix Flink Java Runner test flake: Could not find Flink job #15107
Conversation
Run Java PreCommit |
Java PreCommit replicating the error using a loop Java PreCommit with possible fix with the same loop (Without FlinkSavepointTest error)
Java PreCommit after removing the loop for testing (Without FlinkSavepointTest error) |
Run Java PreCommit |
Run Python_PVR_Flink PreCommit |
Run Portable_Python PreCommit |
Run Java PreCommit |
R: @tvalentyn. Would you help me to review 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.
LGTM
Run Portable_Python PreCommit |
1 similar comment
Run Portable_Python PreCommit |
Thanks, @ibzib! |
… Flink job (apache#15107)" This reverts commit f077ba5.
…ob (apache#15107) * [BEAM-10955] Testing could not find Flink job * [BEAM-10955] Add waitJobToBeReady call, test fix for Flink job not found flakiness * [BEAM-10955] Remove unused import * [BEAM-10955] Discard changes in website folder, remove loop used for testing
…ob (apache#15107) * [BEAM-10955] Testing could not find Flink job * [BEAM-10955] Add waitJobToBeReady call, test fix for Flink job not found flakiness * [BEAM-10955] Remove unused import * [BEAM-10955] Discard changes in website folder, remove loop used for testing
Testing flakiness in Java Precommit: could not find Flink job
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
R: @username
).[BEAM-XXX] Fixes bug in ApproximateQuantiles
, where you replaceBEAM-XXX
with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.CHANGES.md
with noteworthy changes.See the Contributor Guide for more tips on how to make review process smoother.
ValidatesRunner
compliance status (on master branch)Examples testing status on various runners
Post-Commit SDK/Transform Integration Tests Status (on master branch)
Pre-Commit Tests Status (on master branch)
See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.
GitHub Actions Tests Status (on master branch)
See CI.md for more information about GitHub Actions CI.