-
Notifications
You must be signed in to change notification settings - Fork 3.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
cluster: use WaitConditionNextExit #60781
Conversation
There is a chance that this will address an issue that causes spurious failures on CI, where it looks like we're janking the file system out from under a running process. For context, see: cockroachdb#58955 Release note: None
No idea what this is but it's not this PR: @postamar git blame shows you as touching this last, is this something you could route?
bors r=rickystewart |
Build failed: |
bors r=rickystewart
…On Fri, Feb 19, 2021, 18:26 craig[bot] ***@***.***> wrote:
Build failed:
- GitHub CI (Cockroach)
<https://teamcity.cockroachdb.com/viewLog.html?buildId=2695259&buildTypeId=Cockroach_UnitTests>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#60781 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABGXPZARVXMWWZLOYAQK3LLS72NLJANCNFSM4X366TDA>
.
|
Build failed (retrying...): |
If this fails again due to something clearly unrelated, please merge again.
I'm out for the weekend.
…On Fri, Feb 19, 2021, 21:06 craig[bot] ***@***.***> wrote:
Build failed (retrying...):
- GitHub CI (Cockroach)
<https://teamcity.cockroachdb.com/viewLog.html?buildId=2695716&buildTypeId=Cockroach_UnitTests>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#60781 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABGXPZHOU3UVTOL7F3FNRLDS73ADBANCNFSM4X366TDA>
.
|
Build succeeded: |
Thanks for reporting this. This failure was ultimately caused by |
There is a chance that this will address an issue that causes spurious
failures on CI, where it looks like we're janking the file system out
from under a running process. For context, see:
#58955
Release note: None