[SPARK-54989][PYTHON][TEST] Improve eventually util #53755
Closed
+12
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
JIRA Issue Information=== Test SPARK-54989 === This comment was automatically generated by GitHub Actions |
zhengruifeng
approved these changes
Jan 12, 2026
allisonwang-db
approved these changes
Jan 12, 2026
Contributor
|
merged to master |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
quietarg toeventuallyand default toTrue- it should not print attempts be defaultintervalcontrollable and set default to0.1instead of0.01.0.1is pretty fast in our tests.0.01is a bit too much.Why are the changes needed?
When I worked with
eventuallyin my previous experience, it filled my screen and I can't check other information. Most of the time we don't care how many attempts there are.Does this PR introduce any user-facing change?
No
How was this patch tested?
Locally it does not print stuff anymore by default.
Was this patch authored or co-authored using generative AI tooling?
No