-
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
roachtest: acceptance/gossip/peerings failed #56967
Comments
(roachtest).acceptance/gossip/peerings failed on master@7ae56ff64af31b33a7c403aa206495c845773ade:
More
Artifacts: /acceptance/gossip/peerings See this test on roachdash |
(roachtest).acceptance/gossip/peerings failed on master@7ae56ff64af31b33a7c403aa206495c845773ade:
More
Artifacts: /acceptance/gossip/peerings See this test on roachdash |
(roachtest).acceptance/gossip/peerings failed on master@f5f0f11d6e31a6667fe1cafa46cd1a472df38f76:
More
Artifacts: /acceptance/gossip/peerings See this test on roachdash |
(roachtest).acceptance/gossip/peerings failed on master@f5f0f11d6e31a6667fe1cafa46cd1a472df38f76:
More
Artifacts: /acceptance/gossip/peerings See this test on roachdash |
(roachtest).acceptance/gossip/peerings failed on master@f5f0f11d6e31a6667fe1cafa46cd1a472df38f76:
More
Artifacts: /acceptance/gossip/peerings See this test on roachdash |
I've looked at one of the failures and it looks like there's a problem in the test teardown, where one node is found to be dead after the test has otherwise succeeded. I don't know if the test should be expecting that or not. |
Fixed by #57003 |
(roachtest).acceptance/gossip/peerings failed on master@2d8843948d56c789fe7b9cfed515cc8964bde512:
More
Artifacts: /acceptance/gossip/peerings
See this test on roachdash
powered by pkg/cmd/internal/issues
The text was updated successfully, but these errors were encountered: