-
Notifications
You must be signed in to change notification settings - Fork 3.9k
roachtest: gossip/chaos/nodes=9 failed #37118
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
Comments
Parameters: To repro, try:
Failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=1264632&tab=buildLog
|
Parameters: To repro, try:
Failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=1266041&tab=buildLog
|
|
Grab the debug logs. There should be an indication of gossip connectivity
changing. Difficult part is to figure out why. Did this happen on a sha
with Tobi’s RPC fix? I’d cast my suspicions in that direction.
…On Tue, Apr 30, 2019 at 4:44 PM Andrei Matei ***@***.***> wrote:
gossip.go:67,gossip.go:104,gossip.go:116,gossip.go:125,test.go:1253:
gossip did not stabilize in 20.8s
@petermattis <https://github.com/petermattis> what do we do?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#37118 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABPJ754PWKMDQZWCMM7IH43PTCVTDANCNFSM4HIKRLNA>
.
|
The last failure did not include #37204, so it's possible that that fixed the problem. I'd wait and see, at the past rate we should be seeing another failure within a week if the problem persists. |
Parameters: To repro, try:
Failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=1283539&tab=buildLog
|
Some ssh flakes (cc #36929) but we didn't see the stabilization failure again, so closing. |
SHA: https://github.com/cockroachdb/cockroach/commits/99306ec3e9fcbba01c05431cbf496e8b5b8954b4
Parameters:
To repro, try:
Failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=1260033&tab=buildLog
The text was updated successfully, but these errors were encountered: