-
Notifications
You must be signed in to change notification settings - Fork 456
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
wait for tenant to be active before polling for timeline absence #4856
Conversation
1240 tests run: 1189 passed, 0 failed, 51 skipped (full report) |
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.
Changes look good, but wondering about the timeout being enough.
039fce1
to
f0d10d9
Compare
Re-running. |
Re: timeouts, adding this one here as well: https://neon-github-public-dev.s3.amazonaws.com/reports/pr-4857/5718388045/index.html#suites/f588e0a787c49e67b29490359c589fae/5ef37c7fda6cfb7f TL;DR: another tenant load not completing in 2s, this time aiming for Broken. I think we should raise all timeouts to 10 seconds on tests which are also ran against real_s3. |
I'll rerun workflow for several times to be sure that the fix helped |
0b640b1
to
66d8577
Compare
Problem
https://neon-github-public-dev.s3.amazonaws.com/reports/main/5692829577/index.html#suites/f588e0a787c49e67b29490359c589fae/4c50937643d68a66
Summary of changes
wait for tenant to be active after restart before polling for timeline absence