-
Notifications
You must be signed in to change notification settings - Fork 98
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
unexpected E2E test failure #1480
Comments
This looks like a Tendermint bug:
|
I reproduced this as well but rerunning the tests resulted in a pass. |
Need to set |
thank you @ebuchman for fixing this |
this is still an issue 😭 |
So there's a known bug in Tendermint that's causing us to dial peers we're already connected to and fail to connect to them (tendermint/tendermint#2716), but that shouldn't be causing issues with the chain halting. I'm not sure how to understand the output we're seeing in CI, eg. from the link David posted with the failure:
Failing to dial the peer wouldn't crash the app. What does |
Here you go: https://9475-99653950-gh.circle-artifacts.com/0/home/circleci/project/testArtifacts/node_home_2/process.log We record all the logs and node folders in the e2e tests |
So I'm not seeing any issues in that log.
It committed 240 blocks over the 2-minutes in that log, so I'm not sure how to understand what the test is saying actually went wrong? |
I see the error. We fail the script if the outputs see an error. There are errors, but those are not breaking the node. My apologies. I will change this today. |
The text was updated successfully, but these errors were encountered: