-
Notifications
You must be signed in to change notification settings - Fork 473
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
test_runner: improve wait_until
#9936
Conversation
7018 tests run: 6710 passed, 0 failed, 308 skipped (full report)Code coverage* (full report)
* collected from Rust tests only The comment gets automatically updated with the latest test results
5e7ca9d at 2024-12-02T10:26:58.081Z :recycle: |
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'm in favour, always found this function kind of weird.
One note of caution: the use of defaults in so many places means that these default values are going to become somewhat sacred, as ever changing them will likely destabilise some tests.
Yeah, that's always a risk here. I figure 20 seconds is enough to cover practically all common cases and still low enough not to be annoying. Many of the explicit timeouts were also either 20 or 30 seconds, and this seemed to have been mostly arbitrary. |
Will hold off on this until Monday, to avoid any weekend CI breakage. |
Improves `wait_until` by: * Use `timeout` instead of `iterations`. This allows changing the timeout/interval parameters independently. * Make `timeout` and `interval` optional (default 20s and 0.5s). Most callers don't care. * Only output status every 1s by default, and add optional `status_interval` parameter. * Remove `show_intermediate_error`, this was always emitted anyway. Most callers have been updated to use the defaults, except where they had good reason otherwise.
Improves
wait_until
by:timeout
instead ofiterations
. This allows changing the timeout/interval parameters independently.timeout
andinterval
optional (default 20s and 0.5s). Most callers don't care.status_interval
parameter.show_intermediate_error
, this was always emitted anyway.Most callers have been updated to use the defaults, except where they had good reason otherwise.