-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
[Ray release test infra] Change exponential_backoff_retry to use error instead of info on failure #32014
[Ray release test infra] Change exponential_backoff_retry to use error instead of info on failure #32014
Conversation
release/ray_release/util.py
Outdated
@@ -121,7 +121,7 @@ def exponential_backoff_retry( | |||
retry_cnt += 1 | |||
if retry_cnt > max_retries: | |||
raise | |||
logger.info( | |||
logger.warn( |
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.
do you know if warn
will print to the logs? should I use exception
or error
instead cc @krfricke
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.
actually, gunna go for exception
, if we have spammy logs due to this can revisit
Signed-off-by: Cade Daniel <cade@anyscale.com>
c490ce7
to
f3347ef
Compare
@krfricke when will this commit be used for release tests? The logs are still obscured in a failure from the most recent weekly test but looking at git log, this PR is included in the weekly tests. https://gist.github.com/cadedaniel/c85c9af3f901e127dee773f9fcdac367
is this an issue with my PR or has the release test infra not yet picked up my changes? |
This should be picked up but I think the code is just not invoked in this path. @xwjiang2010 is working on similar fix for this issue: #32055 |
…info on failure (ray-project#32014) It appears the root cause of flaky failures described in ray-project#31981 is suppressed because we're not logging exceptions in `exponential_backoff_retry`. Signed-off-by: Cade Daniel <cade@anyscale.com> Signed-off-by: Edward Oakes <ed.nmi.oakes@gmail.com>
It appears the root cause of flaky failures described in #31981 is suppressed because we're not logging exceptions in
exponential_backoff_retry
.Testing